U lu f@sdZddlmZddlmZddlmZmZmZm Z GdddeZ Gddde eZ Gd d d e e Z Gd d d e eZ dd d gZd S)z%MonitoredQueue classes and functions.)PUB)monitored_queue) ProcessProxyProxy ProxyBase ThreadProxyc@s0eZdZdZdZdZeddfddZddZd S) MonitoredQueueBasez"Base class for overriding methods.sinsoutcCs"tj||||d||_||_dS)N)in_typeout_typemon_type)r__init__ _in_prefix _out_prefix)selfr r r Z in_prefixZ out_prefixrD/tmp/pip-unpacked-wheel-h6ekxre8/zmq/devices/monitoredqueuedevice.pyr szMonitoredQueueBase.__init__cCs&|\}}}t||||j|jdS)N)Z_setup_socketsrrr)rZinsZoutsZmonsrrr run_deviceszMonitoredQueueBase.run_deviceN) __name__ __module__ __qualname____doc__rrrr rrrrrr s rc@seZdZdZdS)MonitoredQueueaUClass for running monitored_queue in the background. See zmq.devices.Device for most of the spec. MonitoredQueue differs from Proxy, only in that it adds a ``prefix`` to messages sent on the monitor socket, with a different prefix for each direction. MQ also supports ROUTER on both sides, which zmq.proxy does not. If a message arrives on `in_sock`, it will be prefixed with `in_prefix` on the monitor socket. If it arrives on out_sock, it will be prefixed with `out_prefix`. A PUB socket is the most logical choice for the mon_socket, but it is not required. Nrrrrrrrrrsrc@seZdZdZdS)ThreadMonitoredQueuezcRun zmq.monitored_queue in a background thread. See MonitoredQueue and Proxy for details. Nrrrrrr/src@seZdZdZdS)ProcessMonitoredQueuezbRun zmq.monitored_queue in a separate process. See MonitoredQueue and Proxy for details. Nrrrrrr6srN)rZzmqrZzmq.devices.monitoredqueuerZzmq.devices.proxydevicerrrrrrrr__all__rrrrs