Sure, but we should hash out what the best solution is. The Java binding has done more wrapping than the C/C++ underlying ZeroMQ code so to expose all of the functionality we either do some unwrapping (or just expose the details by making them public), or we write additional wrapper functions (e.g. deregister()). The latter is probably the more "Javaesque" way of handling things, but given that ultimately the Java binding is just a JNI wrapper around the C++ code, it may make more sense to make it more C++-like and just make those underlying structures public so that the two sides are better matched.
What do you think?
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
