B @\@sjdZddlmZmZmZmZddlZeeZ ddl m Z ddl m Z ddlmZd ZGd d d eZdS) zR Encapsulate handling of all Bokeh Protocol messages a Bokeh server may receive. )absolute_importdivisionprint_functionunicode_literalsN)gen) ServerSession) ProtocolError)ProtocolHandlerc@s4eZdZdZddZejddZejddZdS) r a A Bokeh server may be expected to receive any of the following protocol messages: * ``EVENT`` * ``PATCH-DOC`` * ``PULL-DOC-REQ`` * ``PUSH-DOC`` * ``SERVER-INFO-REQ`` The job of ``ProtocolHandler`` is to direct incoming messages to the right specialized handler for each message type. When the server receives a new message on a connection it will call ``handler`` with the message and the connection that the message arrived on. Most messages are ultimately handled by the ``ServerSession`` class, but some simpler messages types such as ``SERVER-INFO-REQ`` may be handled directly by ``ProtocolHandler``. Any unexpected messages will result in a ``ProtocolError``. cCsHt|_tj|jd<tj|jd<tj|jd<|j|jd<tj|jd<dS)Nz PULL-DOC-REQzPUSH-DOCz PATCH-DOCzSERVER-INFO-REQZEVENT)dict _handlersrZpullpushZpatch_server_info_reqZevent)selfrtd|y|||V}WnVtk r}z8td||tjd|j |j dd||t |}Wdd}~XYnXt |dS)aI Delegate a received message to the appropriate handler. Args: message (Message) : The message that was receive that needs to be handled connection (ServerConnection) : The connection that received this message Raises: ProtocolError Nz%s not expected on serverzerror handling message %r: %rz message header %r content %rr)exc_info)r getZmsgtypeZrevisionr ExceptionlogerrordebugheaderZcontentreprrReturn)rmessage connectionZhandlerZworkerrrhandleKs "zProtocolHandler.handlecCst|jd|jddS)NzSERVER-INFO-REPLYZmsgid)rrZprotocolZcreater)rrrrrrrksz ProtocolHandler._server_info_reqN) __name__ __module__ __qualname____doc__rr coroutiner rrrrrr -s  r )r$Z __future__rrrrZloggingZ getLoggerr!rZtornadorZsessionrZprotocol.exceptionsr __all__objectr rrrr s