-eKUdZddlmZddlZejeZddlZddlm Z m Z m Z m Z m Z ddlmZddlmZmZe r ddlmZdd lmZd Ze eefZd ed <Gd dZdS)zn Assemble WebSocket wire message fragments into complete Bokeh Server message objects that can be processed. ) annotationsN) TYPE_CHECKINGAnyCallableUnioncast)ValidationError) BufferHeaderMessage) TypeAlias)Protocol)Receiverr FragmentceZdZUdZded<ded<ded<ded <ded <ddZddZd dZd dZd dZ d dZ d dZ d!dZ d"dZ d#dZdS)$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. zCallable[[Fragment], None]_current_consumerzlist[Fragment] _fragmentsMessage[Any] | None_messagezBufferHeader | None _buf_header_partialprotocolrreturnNonecV||_|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)selfrs 7lib/python3.11/site-packages/bokeh/protocol/receiver.py__init__zReceiver.__init__ps1"!%  fragmentrc>K|||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. )rrrr"s rconsumezReceiver.consume~s$ x(((}r!cpd|_d|_||g|_|j|_dSN)rr _assume_textr _METADATArr$s rrzReceiver._HEADERs8  ,,X667!%r!c|||}|j||j|_dSr')r(rappend_CONTENTr)rr"metadatas rr)zReceiver._METADATAs;$$X.. x(((!%r!c|}j|fdjddD\}}}j|||_dS)Nc3BK|]}|VdSr')r().0xrs r z$Receiver._CONTENT..s13f3fQD4E4Ea4H4H3f3f3f3f3f3fr!)r(rr+rassembler_check_complete)rr"content header_json metadata_json content_jsons` rr,zReceiver._CONTENTs##H-- w'''3f3f3f3fRVRabdcdbdRe3f3f3f0 ]L// ]LYY  r!ctj||}t|dhkrt d|||_|j|_dS)NidzMalformed buffer header )jsonloadsr(setr r_BUFFER_PAYLOADr)rr"headers r_BUFFER_HEADERzReceiver._BUFFER_HEADERsbD--h7788 v;;D( " "!"GV"G"GHH H!!%!5r!c,||}|jtdt|jd}t t t |j||| dS)Nz=Consuming a buffer payload, but current buffer header is Noner;)r;) _assume_binaryrr r rr rrassemble_bufferr5)rr"payloadr@s rr?zReceiver._BUFFER_PAYLOADs%%h//   #!"abb b!1$!7888 WS\4=))99&'JJJ r!cx|jr&|jjr|j|_|j|_dS|j|_dSr')rcompleterrrrA)rs rr5zReceiver._check_completesB = 9T]3 9 MDM%)\D " " "%)%8D " " "r!strcht|tstd|jj|S)Nz8expected text fragment but received binary fragment for ) isinstancerHr r__name__r$s rr(zReceiver._assume_texts8(C(( @!"~]a]s]|"~"~ r!bytescht|tstd|jj|S)Nz8expected binary fragment but received text fragment for )rJrLr rrKr$s rrCzReceiver._assume_binarys8(E** @!"~]a]s]|"~"~ r!N)rrrr)r"rrr)r"rrr)rr)r"rrrH)r"rrrL)rK __module__ __qualname____doc____annotations__r r%rr)r,rAr?r5r(rCr!rrr=s'**X2111!!!!$$$$!!!!         0000 //// 66669999 r!r)rP __future__rlogging getLoggerrKlogr<typingrrrrr exceptionsr messager r typing_extensionsr r__all__rHrLrrQrrRr!rr]sK#"""""g!! ('''''********++++++  CJ'''''BBBBBBBBBBr!