rfc:http-interface
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| rfc:http-interface [2014/10/31 03:19] – googleguy | rfc:http-interface [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 106: | Line 106: | ||
| } | } | ||
| </ | </ | ||
| + | |||
| + | ===== Implementation ===== | ||
| + | |||
| + | It appears the SAPI_API to the incoming HTTP request to PHP is already capable of allowing things such as register callbacks for the header, setting different content_type handlers/ | ||
| + | |||
| + | * http:// | ||
| + | * http:// | ||
| + | |||
| + | |||
| + | This can be easily achieved by providing a direct interface to the internal API through a new class that will then be called along with the SAPI API on RINIT stage. | ||
| + | |||
| ===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
| Line 142: | Line 153: | ||
| ===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
| - | |||
| - | |||
| - | ===== Implementation ===== | ||
rfc/http-interface.1414725558.txt.gz · Last modified: 2017/09/22 13:28 (external edit)