ok i appreciate the input, but for now i will stick with the comet approach because i read that websocket for tomcat 7 is still experimental and i already built a lot of logic around the comet approach. does anyone know the answer to my original question?
On Sat, Jul 14, 2012 at 1:07 PM, Christopher Schultz < [email protected]> wrote: > André, > > On Jul 14, 2012, at 6:03, André Warnier <[email protected]> wrote: > > > Elias Kopsiaftis wrote: > >> Well basically, For the output servlet, I am using comet to keep the > >> connection alive and push things out to the client when they are > available. > >> This program is a chat program with a drawing capability, so two people > can > >> draw on the same canvas and chat with each other. > > > > Isn't this just the kind of thing that "websocket(s)" is supposed to be > made for ? > > Comet is basically a precursor to Websocket: the ideas are vaguely the > same and the use cases are nearly identical. > > Elias, if I were you, I would focus on Websocket moving forward... Comet > is going to see less and less action (globally, not just in Tomcat) a time > goes on. > > -chris > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
