Just a thought; but does nanomsg interoperate nicely with protobuf?-Dan
I'd stick with zmq, particularly considering that you've already begun
updating the egg. It also looks like it has a greater amount of
community and developer support.
-Dan
Matt Gushee m...@gushee.net writes:
On Thu, Mar 5, 2015 at 6:18 PM, Dan Leslie d...@ironoxide.ca wrote:
You might
Hello, folks--
I am developing a distributed application for which I would like to use
ZeroMQ. I've discovered, however, that the zmq egg is unmaintained and very
out of date (the egg is compatible with libzmq 2.x, while the current
stable version of the C library is 4.05).
The good news is that
Hi, Evan--
On Thu, Mar 5, 2015 at 6:13 PM, Evan Hanson ev...@foldling.org wrote:
Does a size_t argument require any special handling on the Chicken
side? Or can I just treat it as a regular integer?
A regular size_t, even: http://api.call-cc.org/doc/foreign/types/size_t
Thanks, but I
On Thu, Mar 5, 2015 at 6:18 PM, Dan Leslie d...@ironoxide.ca wrote:
You might want to consider the nanomsg egg, which doesn't appear to have
a wiki page yet.
https://github.com/Adellica/chicken-nanomsg
Oh, great, yet another alternative to consider! :-/ Well, maybe. I've
never heard of
You might want to consider the nanomsg egg, which doesn't appear to have
a wiki page yet.
https://github.com/Adellica/chicken-nanomsg
-Dan
Matt Gushee m...@gushee.net writes:
Hello, folks--
I am developing a distributed application for which I would like to use
ZeroMQ. I've discovered,
On Thu, Mar 05, 2015 at 06:24:26PM -0700, Matt Gushee wrote:
Thanks, but I guess my question wasn't sufficiently clear. My updated code
already has:
*(foreign-lambda int zmq_recv socket message size_t int); and
(foreign-lambda int zmq_send socket message size_t int)*
What I was
