In this case, would it be possible for the client to check how many connections are unused (via, say, JavaScript) and disabling longpoll on new tabs if there's less than X connections left?
On Sat, 2012-02-18 at 13:54 +0700, Stuart Bishop wrote: > On Fri, Feb 17, 2012 at 6:34 AM, Robert Collins > <robe...@robertcollins.net> wrote: > > I think we should disable longpoll; its not finished, noone is working > > on it, and it causes semi-regular confusion for folk in the LP team > > when they cannot use code.launchpad.net. > > > > Any objections? [I'm not proposing removing the code yet]. > > It is sad, because it is one of those bits of infrastructure we need > but it is always going to be quicker to hack together a poor > implementation for a feature that needs it rather than do the work to > get it into a usable state for all the future features that need it. > > I was saddened to learn that it wasn't operational (despite me seeing > it in action regularly and having seen demonstrations of it working) > after recommending it to jml for one of his projects. jono's trophies > work could also make use of it - rabbit->world gateway is useful. But > I expect both with just go with polling or web scraping if it is not > up to spec in time. > > The nasty open bug being described here seems to be a client side > issue (opening all available connections to a domain and holding them > open, rather than dropping occasionally to let others use a connection > or wildcard domain magic to work around the limit), so the server side > is just fine? > _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
