Francis,
Ok, It shouldn't be a negotiation but an indication to accommodate
communication to each party.
Fair point.
Ok, it is important to note the peer is limiting max frame
size not the
message size which may be still infinite in practical terms (63
bits)and we have fragmentation
Francis et al,
not also that the protocol does support fragmentation and a 1004 frame
too large error.
Even the 1004 error does not carry an indication of what an acceptable
size is, so the client/tool/intermediary that receives a 1004 will
either have to fail or guess a smaller frames size -
[mailto:hybi-boun...@ietf.org] On
Behalf Of Francis Brosnan Blazquez
Sent: 12 July 2011 15:14
To: Hybi
Cc: ietf@ietf.org; draft-ietf-hybi-thewebsocketproto...@tools.ietf.org
Subject: Re: [hybi] Last Call:
draft-ietf-hybi-thewebsocketprotocol-10.txt (The WebSocket
protocol) to Proposed Standard
-thewebsocketprotocol-10.txt (The WebSocket
protocol) to Proposed Standard: request for max frame size
Francis et al,
not also that the protocol does support fragmentation and a 1004 frame
too large error.
Even the 1004 error does not carry an indication of what an acceptable
size is, so the client/tool
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
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..
That was my feeling on it.
I'm a little wary of intermediaries being allowed to adjust
this
: ietf@ietf.org; draft-ietf-hybi-thewebsocketproto...@tools.ietf.org
Subject: Re: [hybi] Last Call:
draft-ietf-hybi-thewebsocketprotocol-10.txt (The WebSocket
protocol) to Proposed Standard: request for max frame size
Hi,
Recently, I posted [1] that websocket protocol should
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
