For the first time I did some experiments with the inproc transport. My experiences lead me to suggest that we should rename inproc (for "inprocess" or inter-thread) to "incontext".
You see, sockets that bind/connect to an inproc transport can *only* do so within the same context. Attempting to connect sockets between contexts using this transport does *not* work. Obviously, a single process may have multiple contexts, so the transport name isn't quite accurate. Thoughts? cr _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
