There is a browser-imposed limit of 2 connections to the same host/port at once, no matter how may browser windows are open (it's a browser-wide limit, not a per window limit.) Thus, Lift detects multiple comet requests on the same app and "does the right thing" which is to turn the long-poll into a short poll.
There is a way around this issue if you want to have a fancy DNS set-up, but the default behavior is to make sure the browser's connections never get clogged up. On Sat, Nov 8, 2008 at 1:11 PM, Piotr Sarnacki <[EMAIL PROTECTED]> wrote: > > Hi, > > I was testing comet and chat demo and after opening 4 or 5 windows > AJAX requests started to end after 500-700ms, rather than 10 seconds. > I know that in most cases this is not an issue (who wants to open 4 > chat windows?), but I'm curious what is the problem here. I think > that's it's not jQuery related problem. I'm not a scala programmer > (yet :) - is there anything with comet implementation that may cause > such a behaviour? > > Cheers > > > > -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
