On Jan 20, 2009, at 11:38 AM, Caleb Richardson wrote:
> We're considering using Resin's comet implementation in an HTTP idle
> scenario (probably 30 minute wait period), where an HTTP client
> creates
> a connection and then waits up to 30 minutes for a response.
Hmm. I think that's true. I'
We're considering using Resin's comet implementation in an HTTP idle
scenario (probably 30 minute wait period), where an HTTP client creates
a connection and then waits up to 30 minutes for a response.
I understand that one of the idle connections takes up a socket on the
server but not a threa
