On May 5, 2008, at 2:20 PM, wesley wrote:
> I've experienced the same problem.
> <thread-max> is set to 2048 in resin.conf and I could not run more
> than 2048
> simultaneous comet clients because of the blocking IO.
> Any ideas?
As long as you're returning from the resume call, the comet support
doesn't use a thread. So there's no blocking I/O at all, and thread-
max shouldn't apply.
The only place where non-blocking I/O would apply would be for reads,
and Resin's comet doesn't currently support async reads.
> ----- Original Message -----
> From: "Tim Perrett" <[EMAIL PROTECTED]>
> To: <email@example.com>
> Sent: Tuesday, May 06, 2008 5:12 AM
> Subject: [Resin-interest] Does Resin comet support work with non-
>> Hey Guys,
>> I wonder, does anyone know if Resin's comet support works with non-
>> blocking IO? What are peoples experiences with Resin's comet support?
>> Cheers, Tim
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list