Peter Kennard wrote:
Hmm I woudl have thought otherwise, since after reading the protocol it
seems specificly designed to support keeping connection alive.
That a sender would keep a "pool" of available connections and when a
hit comes in "get" one which is already connected, and push the request
out, and the destination looks up the servlet and dispatches to it
(until the request is complete), and when complete, releases the still
open connection so the sender and can recycles it back into its pool
without "disconnecting" ie: socket remains open. and there is some
huristic for culling excess connections after heavy traffic may hve
opened more than configured.
Anyway that is what I would do ;^>
And that's what it does :)
If by "multiplexing" you thought interleaving routed packets for
simultaneous "hits" on one pipe I didn't mean that.
Yes, that's how I interpreted your question concerning "multiplexing".
PK
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
