File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/zmq/devices/__pycache__/monitoredqueuedevice.cpython-310.pyc
Back
o ;j� � @ s� d Z ddlmZ ddlmZ ddlmZmZmZm Z G dd� de�Z G dd� de e�Z G d d � d e e �Z G d d � d e e�Z g d �ZdS )z%MonitoredQueue classes and functions.� )�PUB)�monitored_queue)� ProcessProxy�Proxy� ProxyBase� ThreadProxyc @ s0 e Zd ZdZdZdZeddfdd�Zdd� Zd S ) �MonitoredQueueBasez"Base class for overriding methods.� s ins outc C s" t j| |||d� || _|| _d S )N)�in_type�out_type�mon_type)r �__init__� _in_prefix� _out_prefix)�selfr r r Z in_prefixZ out_prefix� r �T/opt/saltstack/salt/lib/python3.10/site-packages/zmq/devices/monitoredqueuedevice.pyr s zMonitoredQueueBase.__init__c C s& | � � \}}}t|||| j| j� d S )N)Z_setup_socketsr r r )r ZinsZoutsZmonsr r r � run_device s z MonitoredQueueBase.run_deviceN) �__name__� __module__� __qualname__�__doc__r r r r r r r r r r s � r c @ � e Zd ZdZdS )�MonitoredQueueaU Class 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. N�r r r r r r r r r � r c @ r )�ThreadMonitoredQueuezcRun zmq.monitored_queue in a background thread. See MonitoredQueue and Proxy for details. Nr r r r r r . r r c @ r )�ProcessMonitoredQueuezbRun zmq.monitored_queue in a separate process. See MonitoredQueue and Proxy for details. Nr r r r r r 5 r r )r r r N)r Zzmqr Zzmq.devices.monitoredqueuer Zzmq.devices.proxydevicer r r r r r r r �__all__r r r r �<module> s
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings