![]() Pyzmq cannot parse monitor messages from libzmq prior to 4.0. While this function is available from libzmq 3.2, See libzmq docs for zmq_monitor for details. Start publishing socket events on inproc. Returns a context manager which will call disconnect on exit. If this is notĬalled, the socket will automatically be closed when it is This can be called to close the socket by hand. Only after all messages are delivered or discarded by reaching the socket’s LINGER timeout Note: closing a zmq Socket may not close the underlying sockets If linger is specified, LINGER sockopt will be set prior to closing. ZMQBindError – if max_tries reached before successful bind close ( linger = None ) → None ¶ Max_tries ( int, optional) – The maximum number of bind attempts to make. Max_port ( int, optional) – The maximum port in the range of ports to try (exclusive). Min_port ( int, optional) – The minimum port in the range of ports to try (inclusive). ParametersĪddr ( str) – The address string without the port to pass to Socket.bind(). If the port range is unspecified, the system will choose the port. bind_to_random_port ( addr : str, min_port : int = 49152, max_port : int = 65536, max_tries : int = 100 ) → int ¶īind this socket to a random port in a range. ![]() If the address is unicode, it isĮncoded to utf-8 first. ParametersĪddr ( str) – The address string. New in version 20.0: Can be used as a context manager. The address of the underlying libzmq context The context will automatically be closed when it is garbage collected. This can be called to close the context by hand. Or the socket’s linger period set with the zmq.LINGER socket option has expired.įor further details regarding socket linger behaviour refer to libzmq documentation for ZMQ_LINGER. Physically transferred to a network peer,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |