Rustam Abdullaev wrote:
"Paul Querna" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
The event mpm is likely the right place to start since it already have a
concept of suspendable 'conections', but how it is done is specific to
HTTP., However, the problems with making a suspendable *request* are much
deeper in the other parts of the core, and less of a problem in the MPMs.
...
Thanks for the info! Now that I think about it, I could actually live with
suspendable connections (not requests).
Is it possible to add some flags to the EOS metadata bucket? For example, to
have a 'continuation' EOS bucket, which would cause the MPM to 'replay' the
original http request after a certain time (or on demand). In essence there
would be 2 separate requests, but they would share the same connection.
To me this looks like a fairly small change to the overall architecture.
Most changes would be inside the Event MPM.
Thoughts? Is this possible?
What you are describing is HTTP Keep Alive[1], and the Event MPM already
does this :-)
-Paul
[1] - http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html
