Ticket filed :) https://issues.apache.org/jira/browse/WICKET-5285
> The browsers have a limit of max opened connections to a domain. > For Firefox and Chrome it is 6 connections. > For IE 7/8 (not sure about the newer versions) it is 2. Interesting, Is this diferent when using websocket? We use JBoss EAP 6.1, so the Atmosphere version included in wicket-atmosphere (1.0.13) don't support JBoss Websockets, it fallsback to streaming and this issue happens, but I tried to implement a websocket based on this https://github.com/Atmosphere/jboss-websockets using a servlet and then this issue don't happens anymore, none of the tabs get blocked. In this test I've not used the jquery.atmosphere javascript, only the servlet implementation and basic Websocket javascript api. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-Atmosphere-Encoding-and-MultiTab-issues-tp4660342p4660474.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
