I'm using long polling in our application and I don't see that one connection per server restriction here. I did however see that safari was not leaving the lo

I'm using long polling in our application and I don't see that one connection per server restriction here. I did however see that safari was not leaving the loading state (and thus not firing any of the loaded events, nor hiding the URL bar) if I started the long polling connection before the page was fully loaded. Once I moved opening the connection to a setTimeout callback inside the onLoad handler (so not DOM ready, but actual load), this went away and the page works normally.