Hi;
So whilst an instance is streaming (from an input steam) a result back
to the client, the socket connection between the Apache adaptor and
the instance is completely dedicated to that job and any other
requests to that instance will be enqueued?
cheers.
Also, when you have larger resources which can't be served from a
cache, it doesn't make much of a difference as you can serve with
a streaming handler.
...
Does "streaming handler" above mean hooking a java.io.InputStream
up to an WOResponse instance? I haven't actually looked at the
Apache module source or done any experiments, but is it true that
the adaptor-instance communication interleaves these requests? I
have previously assumed this was happening.
...
"Interleaves" ? As long as a stream is not empty, it's served more
or less directly to the socket of the client. Also, the app doesn't
really communicate much, it's either servicing a request, in which
case the data gets sent to the client, or it's not doing anything in
which case it's marked as dead for the web server that is currently
trying to contact it. All the other availability stuff is handled
via the wotaskd communication.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
