Hi,
On 1 socket connection, if client sends packet1, packet2, packet3, ...
on the server side, does Grizzly ensure the packets (or the bytes) are
proccessed (pass to the protocol chain) in the order they arrives ? That
is, if I associate a handler object to a CONNECTION scope attribute to
the context, I should see a serialized access to the handler (except on
connection close events) ?
Thanks,
amy