ntation, or it's at the server end.
> >
> > I will make a test case which does exact timing and is separated from our
> > application and report back on what I find.
> >
> > MR
> >
> > On Tue, Jan 29, 2013 at 12:11 PM, Mark Thomas wrote:
> >
&g
oh, and this was using an established connection. text message however.
On Tue, Jan 29, 2013 at 12:19 PM, Michael Roberts wrote:
>
> This was using .35 with the default connector (just a generic tomcat
> install using the installer, on windows 7 64bit) from current firefox. I
> ca
ur
application and report back on what I find.
MR
On Tue, Jan 29, 2013 at 12:11 PM, Mark Thomas wrote:
> On 29/01/2013 20:04, Michael Roberts wrote:
> > I'm seeing some differences in the latency of making a post request via
> > jQuery versus sending a websockets message
I'm seeing some differences in the latency of making a post request via
jQuery versus sending a websockets message. It maybe that this is overhead
in my application caused by processing the json I am sending in the
message, but I find this hard to believe. I imagined that web socket
connection sh
Thanks, comments below. I'm going to address the chat example connection
pruning in a separate mail.
>> 1) In the createWebSocketInbound method implemented by the chat example's
> >> subclass of WebSocketServlet, there is seemingly no way to interrogate
> the
> >> incoming request for information
>
>
> >> 3) As mentioned, the chat example maintains a list of connections.
> >> Connections (MessageInbound instances) are added to this list when
> >> connections are established. However, they are never removed when the
> >> connection is closed, so the list grows. The broadcast method silentl
Hi, I have been playing with the web sockets support in 7.0.27. I have
some comments and, as requested in the readme, am sending them to the dev
list. Caveat: it's been a while since .27, so perhaps some of these issues
are addressed in the nightly builds. Anyhow, here we go:
1) In the createWe
