Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

0MQ 0.5 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News 0MQ 0.5 (Default branch)
# 1  
Old 02-06-2009
0MQ 0.5 (Default branch)
0MQ is a lightweight messaging kernel. It achieves 30 microsecondend-to-end latencies and over 3 million messages per second. It can beused from C, C++, Python, and Java. It runs on AIX, FreeBSD, HP-UX,Linux, MacOS X, OpenBSD, QNX Neutrino, Solaris, and Windows.License: GNU Lesser General Public License (LGPL)Changes:
An auto-reconnect feature improves overallrobustness of the systemand makes it tolerate even network outages andapplication failures.Flow control and queue limits allow you toexplicitly control thesystem in congestion conditions. A .NET extensionprovides accessto the universe of C# and Visual Basic businessapplications, whilemulti-protocol support allows you to leverageadvantages of differentnetworking protocols: ubiquitous TCP, PGM reliablemulticast, AMQPbusiness messaging protocol, and SCTP telephony.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

zmq_inproc

ZMQ_INPROC(7)							    0MQ Manual							     ZMQ_INPROC(7)

NAME

       zmq_inproc - 0MQ local in-process (inter-thread) communication transport

SYNOPSIS

       The in-process transport passes messages via memory directly between threads sharing a single 0MQ context.

	   Note
	   No I/O threads are involved in passing messages using the inproc transport. Therefore, if you are using a 0MQ context for in-process
	   messaging only you can initialise the context with zero I/O threads. See zmq_init(3) for details.

ADDRESSING

       A 0MQ address string consists of two parts as follows: transport://endpoint. The transport part specifies the underlying transport protocol
       to use, and for the in-process transport shall be set to inproc. The meaning of the endpoint part for the in-process transport is defined
       below.

   Assigning a local address to a socket
       When assigning a local address to a socket using zmq_bind() with the inproc transport, the endpoint shall be interpreted as an arbitrary
       string identifying the name to create. The name must be unique within the 0MQ context associated with the socket and may be up to 256
       characters in length. No other restrictions are placed on the format of the name.

   Connecting a socket
       When connecting a socket to a peer address using zmq_connect() with the inproc transport, the endpoint shall be interpreted as an arbitrary
       string identifying the name to connect to. The name must have been previously created by assigning it to at least one socket within the
       same 0MQ context as the socket being connected.

WIRE FORMAT

       Not applicable.

EXAMPLES

       Assigning a local address to a socket.

	   /* Assign the in-process name "#1" */
	   rc = zmq_bind(socket, "inproc://#1");
	   assert (rc == 0);
	   /* Assign the in-process name "my-endpoint" */
	   rc = zmq_bind(socket, "inproc://my-endpoint");
	   assert (rc == 0);

       Connecting a socket.

	   /* Connect to the in-process name "#1" */
	   rc = zmq_connect(socket, "inproc://#1");
	   assert (rc == 0);
	   /* Connect to the in-process name "my-endpoint" */
	   rc = zmq_connect(socket, "inproc://my-endpoint");
	   assert (rc == 0);

SEE ALSO

       zmq_bind(3) zmq_connect(3) zmq_ipc(7) zmq_tcp(7) zmq_pgm(7) zmq(7)

AUTHORS

       This manual page was written by the 0MQ community.

0MQ 2.2.0							    04/04/2012							     ZMQ_INPROC(7)