As said before, making such DNS SRV specification an extension (so
present in other document) will mean no success at all, as WebSocket
client implementors (i.e. webbrowser vendors) will not be mandated to
implement it and service providers could not rely on the support of
DNS SRV in web
Hi Len,
I agree that this would be very useful.
Would this be one frame size for both directions, or could it be specified
in each direction?
It should be done in both directions, assuming each party may have
different requirements..
I'm a little wary of intermediaries being allowed to
(or other mech like ack confirmation, its the same) is like
pretending having a coin with only one side.
Len
www.lenholgate.com
-Original Message-
From: hybi-boun...@ietf.org [mailto:hybi-boun...@ietf.org] On
Behalf Of Francis Brosnan Blazquez
Sent: 12 July 2011 15:14
To: Hybi
Cc
Hi,
Recently, I posted [1] that websocket protocol should include an
indication about max frame size that is willing to accept the connecting
peer.
Many pointed this is not an issue because you could use a stream
oriented API (like TCP send/recv and others), but that only bypasses the
problem
