U /e@sdZddlmZddlZeeZddlmZm Z m Z m Z m Z m Z ddlmZddlmZmZernddlmZd Ze eefZGd d d ZdS) zn Assemble WebSocket wire message fragments into complete Bokeh Server message objects that can be processed. ) annotationsN) TYPE_CHECKINGAnyCallableListUnioncast)ValidationError) BufferHeaderMessage)Protocol)Receiverc@seZdZUdZded<ded<ded<ded <ded <d d d ddZdddddZdd dddZdd dddZdd dddZ dd dddZ dd dddZ d ddd Z dd!dd"d#Z dd$dd%d&Zd'S)(ra Receive wire message fragments and assemble complete Bokeh server message objects. On ``MessageError`` or ``ValidationError``, the receiver will reset its state and attempt to consume a new message. The *fragment* received can be either bytes or unicode, depending on the transport's semantics (WebSocket allows both). .. code-block:: python [ # these are required b'{header}', # serialized header dict b'{metadata}', # serialized metadata dict b'{content}, # serialized content dict # these are optional, and come in pairs; header contains num_buffers b'{buf_header}', # serialized buffer header dict b'array' # raw buffer payload data ... ] The ``header`` fragment will have the form: .. code-block:: python header = { # these are required 'msgid' : # a unique id for the message 'msgtype' : # a message type, e.g. 'ACK', 'PATCH-DOC', etc # these are optional 'num_buffers' : # the number of additional buffers, if any } The ``metadata`` fragment may contain any arbitrary information. It is not processed by Bokeh for any purpose, but may be useful for external monitoring or instrumentation tools. The ``content`` fragment is defined by the specific message type. z$Callable[[Receiver, Fragment], None]_current_consumerzList[Fragment] _fragmentszMessage[Any] | None_messagezBufferHeader | None _buf_header_partialr None)protocolreturncCs$||_|j|_d|_d|_d|_dS)z Configure a Receiver with a specific Bokeh protocol. Args: protocol (Protocol) : A Bokeh protocol object to use to assemble collected message fragments. N) _protocol_HEADERrrrr)selfrr;/tmp/pip-unpacked-wheel-f5fndrjf/bokeh/protocol/receiver.py__init__ns zReceiver.__init__Fragment)fragmentrcs|||jS)a  Consume individual protocol message fragments. Args: fragment (``JSON``) : A message fragment to assemble. When a complete message is assembled, the receiver state will reset to begin consuming a new message. )rrrrrrrconsume|s zReceiver.consumecCs&d|_d|_||g|_|j|_dSN)rr _assume_textr _METADATArrrrrrszReceiver._HEADERcCs"||}|j||j|_dSr!)r"rappend_CONTENTr)rrmetadatarrrr#s  zReceiver._METADATAcsV|}j|fddjddD\}}}j|||_dS)Ncsg|]}|qSr)r").0xrrr sz%Receiver._CONTENT..)r"rr$rZassembler_check_complete)rrcontentZ header_jsonZ metadata_jsonZ content_jsonrr)rr%s   "zReceiver._CONTENTcCs|||_|j|_dSr!)r"r_BUFFER_PAYLOADrrrrr_BUFFER_HEADERs zReceiver._BUFFER_HEADERcCs6||}ttt|jtt|j||dSr!) _assume_binaryrr rrZassemble_bufferr rr,)rrpayloadrrrr.s  zReceiver._BUFFER_PAYLOAD)rcCs,|jr |jjr |j|_|j|_n|j|_dSr!)rZcompleterrrr/r)rrrr,s zReceiver._check_completestrcCs t|tstd|jj|S)Nz8expected text fragment but received binary fragment for ) isinstancer2r r__name__rrrrr"s zReceiver._assume_textbytescCs t|tstd|jj|S)Nz8expected binary fragment but received text fragment for )r3r5r rr4rrrrr0s zReceiver._assume_binaryN)r4 __module__ __qualname____doc____annotations__rr rr#r%r/r.r,r"r0rrrrr;s ,  r)r8 __future__rlogging getLoggerr4logtypingrrrrrr exceptionsr messager r r __all__r2r5rrrrrrs