On Fri, Apr 05, 2002 at 11:10:13PM -0800, Aaron Bannert wrote:
> After working with this filter for the last few days I came to realize
> that it really isn't taking advantage of the newer features of Apache 2.
> In addition it seems to have a flaw that would prevent it from working
> downstream from any other content-generation filter (imagine, for example,
> a mod_include page that embedded PHP script).
>
> I think a good way to take advantage of the filter system would be
> to break the input stream into buckets of two types: constant strings
> and PHP script code. As flex/bison needs to be fed more data (from the
> yyinput function I think it's called) it could just read data out of
> buckets on the brigade. As it generates data, it could spit out buckets
> that are fed back into the brigade and passed downstream. The same
> would happen to the "constant string" data buckets: they could just
> be quickly passed down the filter chain.
>
> Is this feasible in the SAPI domain? I know very little about the
> SAPI, but will it allow me to override the equivalent of the yyinput
> function?
php (in this case the engine) _needs_ the whole script in
order to compile it (before it can start executing).
therefore the apache2 sapi has to read all input from the
filter that's generating data for it. then the script gest
compiled, exeuted and the outpout will be send
bucket-by-bucket to the next filter.
client
|
(some stuff left out)
|
mod_php
|
mod_include
|
file.shtml
so php has to read everything from mod_include before it
starts passing data on.
tc
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
