[hybi] thewebsocketprotocol #40 (new): Clarify binary/utf-8 mixed handling

["hybi issue tracker" <[e-mail]>]

#40: Clarify binary/utf-8 mixed handling

 It can be confusing to mix binary and utf-8 frames in one tcp-like stream.
 For example, what will the current text-only JS Websocket API do if
 suddenly binary starts appearing?
 Additionally, when only partial frames may be available, it is expensive
 to verify that this is indeed a valid UTF-8 stream (protocol
 implementation needs to take into account multi-byte characters and end of
 current data payload).  If binary has been negotiated for this session,
 processing can be optimized accordingly.

 Proposal: allow negotiation to clarify if a stream will not mix binary and
 text in order to enable optimizing for the binary-only case.

-- 
--------------------------------------+-------------------------------------
 Reporter:  g_e_montenegro@…          |       Owner:     
     Type:  defect                    |      Status:  new
 Priority:  major                     |   Milestone:     
Component:  thewebsocketprotocol      |     Version:     
 Severity:  -                         |    Keywords:     
--------------------------------------+-------------------------------------

Ticket URL: <http://wiki.tools.ietf.org/wg/hybi/trac/ticket/40>
hybi <http://tools.ietf.org/hybi/>
The Hypertext-Bidirectional (HyBi) working group will seek
standardization of one approach to maintain bidirectional
communications between the HTTP client, server and intermediate
entities, which will provide more efficiency compared to the current
use of hanging requests.