fdZddlmZddlmZddlmZmZmZm Z GddeZ Gdde eZ Gd d e e Z Gd d e eZ gd Zy)z%MonitoredQueue classes and functions.)PUB)monitored_queue) ProcessProxyProxy ProxyBase ThreadProxyc,eZdZdZdZdZeddfdZdZy)MonitoredQueueBasez"Base class for overriding methods.sinsoutcRtj||||||_||_y)N)in_typeout_typemon_type)r__init__ _in_prefix _out_prefix)selfr rr in_prefix out_prefixs [/var/www/cvtools/html/venv/lib/python3.12/site-packages/zmq/devices/monitoredqueuedevice.pyrzMonitoredQueueBase.__init__s' 48hW#%r cr|j\}}}t||||j|jy)N)_setup_socketsrrr)rinsoutsmonss r run_devicezMonitoredQueueBase.run_devices0--/T4T4$:J:JKr N) __name__ __module__ __qualname____doc__rrrrrr rr r s#,JK+.6&Lr r ceZdZdZy)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. Nrrrr r!r rr#r#s r r#ceZdZdZy)ThreadMonitoredQueuezcRun zmq.monitored_queue in a background thread. See MonitoredQueue and Proxy for details. Nr$r!r rr&r&.r r&ceZdZdZy)ProcessMonitoredQueuezbRun zmq.monitored_queue in a separate process. See MonitoredQueue and Proxy for details. Nr$r!r rr)r)5r'r r))r#r&r)N)r zmqrzmq.devices.monitoredqueuerzmq.devices.proxydevicerrrrr r#r&r)__all__r!r rr.sY+ 6OOLL& '  -{.  Nr