Quick update... I switched the code to using Servlet 3.0 and I can get streaming data from all three browsers on the same machine: Chrome, FireFox, and IE.
I still cannot get two tabs in Chrome or FireFox to stream data, but I think that is simply because they are sharing JSESSIONIDs and I can probably code around that. Thanks... Bill- On Wed, Jan 18, 2012 at 12:13 PM, William Speirs <wspe...@apache.org> wrote: > Thanks for the quick responses, I'll respond to both at once below: > > On Wed, Jan 18, 2012 at 11:56 AM, André Warnier <a...@ice-sa.com> wrote: > > really a second, different browser ? or another window/tab from the same >> browser ? >> (if the second case, it may be re-using the same local IP:port (or just >> the same established connection) to "connect" to the server, and that may >> explain why the server appears not to react. >> > > Yea, Chrome & FireFox... I don't think they share sessions (cookies) or > connections. > > On Wed, Jan 18, 2012 at 12:02 PM, Konstantin Kolinko < > knst.koli...@gmail.com> wrote: > >> The HTTP specification recommends to have no more than 2 active >> connections to the same HTTP server. The web browsers usually respect >> it. >> > > This would be at the 2 connection limit though... > > >> IIRC "the same server" = the same DNS name, so different names have >> different connection limits. >> >> It should be already discussed elsewhere - try to search. > > > Yea, I didn't find anything, but I'll keep looking... > > >> > Running: >> > tomcat-7.0.6 >> >> Too old. >> > > I will certainly upgrade to 7.0.23 and see if that fixes the issue... you > guys move too fast for me :-) > > >> > servlet-api-2.5.jar >> >> Where? >> > > This was included in our pom.xml file as <scope>provided</scope>, which > was blatantly stolen from an example somewhere online. > > > tomcat-*-7.0-SNAPSHOT >> >> Does not make sense. > > > Agreed, but again from Googleing somewhere it stated we should include > this in our pom.xml as required to "make it all work". > > On a more general level, was the Comet implementation in Tomcat simply > a precursor to Servlet 3.0's asynchronous functionality? > > In looking at other examples and reading the overview of the Servlet 3.0 > spec, it seems as though it will do what I want. Why would I use the Comet > stuff in Tomcat? > > My current idea is to use the latest version of Tomcat 7, Servlet 3.0 (ie > dropping servlet-api-2.5 and adding javaee-api-6.0 to my pom.xml) and > implementing something similar to: > http://code.google.com/p/jquery-stream/source/browse/sub-projects/jquery-stream-servlet/trunk/src/main/java/flowersinthesand/example/ChatServlet.java > Does > this seem like a reasonable path forward? > > Thanks again for the quick response... > > Bill- >
