Complaints are not the only (or best) measure of quality.
How many questions does the multitude of semi-redundant functions generate on
this list,
especially from new users trying to get started? (More so, since some functions
take void*
and so can't validate by argument type).
Perhaps it's
like that.
Even a ZeroMQ v5.0 would have to support 3.2 and 2.0 API calls (which
can be taken out of the man pages) unless there is a real, significant
benefit in removing them.
-Pieter
On Thu, Sep 25, 2014 at 8:26 PM, Tim Crowder crowd...@yahoo-inc.com wrote:
Complaints are not the only (or best
Here are a few common choices:
https://github.com/google/flatbuffers/
http://code.google.com/p/protobuf/
https://thrift.apache.org/
http://avro.apache.org/
http://jsoncpp.sourceforge.net/
Protocol buffers are a good general purpose solution,
with good performance, and tons of language
to each.
Cheers;
Jeremy
On 30 May 2014 20:03, Tim Crowder
crowd...@yahoo-inc.commailto:crowd...@yahoo-inc.com wrote:
Hi Jeremy-
You might take a look at existing systems for how they handle it.
Apache Kafka, for instance, always maintains a backlog of messages,
via fast-append to logfiles. Clients
Hi Jeremy-
You might take a look at existing systems for how they handle it.
Apache Kafka, for instance, always maintains a backlog of messages,
via fast-append to logfiles. Clients keep track of the offset of the
last message they processed, and actively pull new messages from
the publisher.
Hi All-
I was looking for a way to manage actions/resources around clients connecting
and
disconnecting from a router socket. Was happy to see the socket-monitor
interface,
but it only gets partway there...
Since the socket-monitor messages deal with file-descriptors as an ID, there
still
