I am having random errors, but we are still looking into them because right
now we think they are probably from our end. The current one is that the
connection from the client to the comet servlet will randomly repeatedly
receive "NULL". Still looking into this to see what the server is doing


On Thu, May 29, 2014 at 3:13 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Elias,
>
> On 5/29/14, 3:08 PM, Elias Kopsiaftis wrote:
> > To make sure it doesnt exist in Tomcat7. Thats why. Ive never
> > looked into the tomcat source code and theres no point for my
> > current project unless this bug still exists. Just trying to save
> > myself the work. Also, I couldnt find a page of known tomcat7 comet
> > issues. If such a page existed it would be helpful
>
> Check Bugzilla. Anything logged and not fixed is "known", I suppose.
>
> Also check the changelogs. Feel free to check everything between Tomat
> 6.0.33 and Tomcat 7.0.54, but that's a lot of reading.
>
> Are you actually having a problem, or are you just scared of what
> might be out there?
>
> To my knowledge, there are no proofs that Tomcat has zero flaws.
> Therefore, it could potentially serve every response to the wrong
> client. Experience says that does not happen. Common sense also tells
> you that, because nobody would use Tomcat if it was so horribly broken.
>
> There have been related bugs in the past that have been fixed when
> found. If you think you have found one, please report it with as much
> information as you can. But if you are just asking if there is a known
> problem with Tomcat where responses go to the wrong client, the answer
> is "no": if we knew about a problem, we'd fix it and roll a new release.
>
> - -chris
>
> > On Thu, May 29, 2014 at 2:45 PM, David kerber
> > <dcker...@verizon.net> wrote:
> >
> >> On 5/29/2014 2:21 PM, Elias Kopsiaftis wrote:
> >>
> >>> oh yea, im on tomcat 7 btw
> >>>
> >>
> >> Then why are you asking about a problem in a very old version of
> >> Tomcat 6?
> >>
> >>
> >>
> >>
> >>>
> >>> On Thu, May 29, 2014 at 2:13 PM, Elias Kopsiaftis
> >>> <yemi...@gmail.com> wrote:
> >>>
> >>> Hey guys,
> >>>>
> >>>> I found this on the web, and it really alarms me because my
> >>>> web app which is in development depends on Comet technology
> >>>> to work.
> >>>>
> >>>>
> >>>> http://bighow.net/4294974-Comet_under_Tomcat_6_0_33_
> >>>> sends_data_to_a_wrong_user.html
> >>>>
> >>>> Before I start digging into the tomcat7 source code, can
> >>>> anyone verify or contest the issue on that site? If Comet is
> >>>> not 100% dependable, how about WebSockets as an alternative?
> >>>>
> >>>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >>
> >>
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJTh4btAAoJEBzwKT+lPKRYhvgQAMO2/TysR56uWeAo3nDRiJZP
> 2R9Q26t0UmAVqbUfujs0VtCGTySv6LKCHgbG6I/XQotSbdeaWY9jIZphqpLxylLV
> T24WqIFAv2J4ZLsx/W09pXMqvErVnp0kuesaFnEj4ooOfqATRTG0oscgQxy6Qrtb
> kzoOHYxG8c0/T/RnvNF+97F3ybRdwpW4U2TwLvtMYCw6H9MSzUPRJLdSIbnA4oS2
> Bf7OcVoHCJ/53ODDuUfTpFXZgEucNmq58HHRaV0TYBQjIv1GwMMe889MWrfIQzuO
> rmHbXqORb/tRTZeV2DxPZ2t3AS0qU6K1qz4SDX91jngMJg9Uclvh8iW5pSi8K5y9
> a9ZGoB4nVX9vZlkLwazfHfvUXwFVfzqZL9yYaSc7cT8EGf/47KV/xjRombdKyw18
> /M4pNEBrD+hOqKKB24J3u6v1aGuz6ffUZ8io94bAGNm+Nq86+cL45PxQ49pkyVIk
> T7FQbM/NDgNJVRdByHalPlPyFtvC4d6mpU+yG9ryyESy1yCyMx9ojNTA/gt0IJ40
> CZdqnPkEAsrzIadRYi/2n3eTQFrABHmH+jfh1ShzxLsd96mxz7GC1DM26yoJq/ok
> ckiEY0zY058Csp1NafRoSKbDSQ48pkvBvF0eccym3fCZwknA22a9iuZ9eRkLXbdO
> NxKin3hu9RQlMzCC1jmI
> =yrsV
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to