Hi:
Architecturally speaking, is there any simple way to modify an sapi
backend to return HTTP headers through the output buffering mechanism?
As far as I can tell, headers are managed seperately by main/output.c,
with php_ub_body_write_no_header being substituted in once the HTTP
headers are
What are you trying to accomplish?
On Sunday, November 24, 2002, at 05:40 PM, David Brown wrote:
Hi:
Architecturally speaking, is there any simple way to modify an sapi
backend to return HTTP headers through the output buffering mechanism?
As far as I can tell, headers are managed seperately
Hi George:
It's something that's probably better solved in user-space, but I
figured I'd poke around anyway. :)
I'm attempting to write a little prefork HTTP server entirely in PHP.
The script instansiates an 'application class', which is persistent
across requests. Output of the application is
Bad idea or not (I don't think it will be fast and there are some
problems with some of the ideas you want to pull off, imho) I
certainly believe that reinventing the wheel can be a healthy exercise.
That having been said, most of what you want to accomplish here
requires a single lon-living
You can probably learn a lot by example. There is a pretty complete
HTTP server written in PHP available here:
http://nanoweb.si.kz/
Chris
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
