Contexts are cheap to create but act as the hub for inproc transport, so you want one context per process.
-Pieter Sent from my Android mobile phone. On Jun 24, 2010 2:23 AM, "Stuart Halloway" <[email protected]> wrote: If the context represents any real resources on the native side, I would recommend going in the opposite direction: (1) Clients should create and hold the context, and explicitly close it when they are done. (2) Ditto for sockets (except that creation is via the context). (3) Neither Context nor Socket should implement finalize. (4) Instead, they should implement the Closeable interface [1]. How costly is the context? Should it be created once per process? Once per thread? Something else? [1] http://java.sun.com/j2se/1.5.0/docs/api/java/io/Closeable.html > On Wed, Jun 23, 2010 at 5:58 PM, gonzalo diethelm <[email protected]> wrote: >>> I think you are o...
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
