Hi James,
the czmqjni wrapper is a very thin layer above the czmq API. So any
example in the
czmq README should work. Though some APIs might not be available in the
wrapper
due to technical reasons. If you're not able to convert the C examples
in the README,
let me know then I'll try to create one later this week.
While the czmq API is stable the jni wrapper's API is not. So we are
happy to receive
improvements.
APIwhise jzmq and jeromq are the same. Also those APIs a more javalike
and both
libraries have been more tested than czmqjni. But they don't support
encryption,
if I'm not mistaken, which would be your reason to use czmqjni instead.
//Kevin
On Di, Apr 11, 2017 at 4:30 , James Gatannah <[email protected]>
wrote:
I've been dabbling with the bindings from github and the source
distribution, and I'm starting to suspect that they aren't in a usable
state yet.
My specific problem is that I can't figure out how to send a message.
The closest I've managed to get is using Zframe.send(), which takes a
long parameter for the destination. If I pass in the Zsocket's .self
member, I get an error about attempting a socket operation on a
non-socket.
Zsock.send() can't possibly work, since it only passes along the first
of the variadic arguments.
I haven't spent much time with Zmsg, since I'm using client/server
socket types, but it seems to have the same problems as Zframe.
Am I missing something obvious? Based on what I've found in the
mailing list archives, it looks like people expect this to work.
I've run across a few other issues that seem like they should be
low-hanging fruit (the "standard" czmq socket creation methods really
should be static, for example), but I've never had a chance to do more
than glance at GSL when I was reading through the Guide the first
time, and I've only briefly glanced at zproject.
And, if this is a stable API, then obviously that part couldn't be
changed anyway (not that that's a barrier to adding appropriate static
methods).
Alternatively, I see a lot of recommendations here to just use jeromq
instead. Does anyone have any recommendations about the difficulty of
implementing CLI/SRV there as opposed to jzmq? As ugly as JNI code and
that build/installation process is, at least I spent some time digging
through that code a few years back.
Thanks,
James
_______________________________________________
zeromq-dev mailing list
[email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
[email protected]
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
