Hi,
I wrote some code to support noncontiguous buffers in message frames -
https://github.com/maxkozlovsky/zeromq4-1/commit/befc4e1c7de
dbf0b9e5641d19e877a19f0f6db16.
Please let me know if you would like to use it in some form, I can get it
to more production quality if necessary.
Max
__
Hi,
Make sure you have ZMQ_ROUTER_HANDOVER option set on the sockets if you
want to reuse the identity across process restarts.
Max
On Tue, Nov 8, 2016 at 12:01 PM, Wilson Chong wrote:
>
> my answer is actually based on my own experience. if i tried using
> "durable" socket by assigning an ide
Hi,
It is kind of tricky.
The availability of data on the file descriptor returned with ZMQ_FD
signals that there is a zmq socket state change, i.e. the receive queue
goes from empty to non-empty. Any operation on the socket
(send/receive/getsockopt with ZMQ_EVENTS) may clear the notification. No
what is expected from real sockets.
On Wed, Nov 16, 2016 at 6:17 PM, Justin Karneges wrote:
> What Max says is true, BUT there is actually a specific bug with inproc
> sockets not working with ZMQ_FD.
>
> (I'm the one that filed the original issue)
>
> On Wed, Nov 16,
Hi,
Would not globally overwriting malloc/free with the custom implementation
achieve the desired behavior (instead of providing hooks for installing
malloc overrides in each and every library)?
Max
On Mon, Nov 28, 2016 at 5:08 AM, Auer, Jens wrote:
> Hi,
>
> I don't see a big problem with the
wants
> a different custom allocator?
>
>
>
> Cheers,
>
> Jens
>
>
>
> *Von:* zeromq-dev [mailto:zeromq-dev-boun...@lists.zeromq.org] *Im
> Auftrag von *Max Kozlovsky
> *Gesendet:* Montag, 28. November 2016 20:36
> *An:* ZeroMQ development list
> *Betreff:* R
memory pool there and standard
> allocators everywhere else. I welcome this flexibility.
>
>
>
> Cheers,
>
> Jens
>
>
>
> *Von:* zeromq-dev [mailto:zeromq-dev-boun...@lists.zeromq.org] *Im
> Auftrag von *Max Kozlovsky
> *Gesendet:* Montag, 28. November 2016 20:4
Hi,
I wonder what is the practical application of this model? If for
correctness of the application it is enough to deliver every message to at
least one of the subscribers, why not always sent just one copy of a
message to just one of the subscribers? Sends to the rest of the
subscribers are over
017-03-07 20:51 GMT+01:00 Max Kozlovsky :
> > I wonder what is the practical application of this model? If for
> correctness
> > of the application it is enough to deliver every message to at least one
> of
> > the subscribers, why not always sent just one copy of a message to
t we care about)
> buffer such as how kafka, eventstore, or chronicle work. This does
> require a switch from push to pull model subscriptions in most cases.
> As example "give me the next 10 messages after #2929292".
>
> Cheers,
>
> Greg
>
> On Thu, Mar 9, 2017 at
wrote:
> Hi Max,
> thanks for your reply. Just a question:
>
> 2017-03-09 16:35 GMT+01:00 Max Kozlovsky :
> > It seems a pull model might be better in this case.
>
> from my understanding, mostly based on reading zeroMQ - the guide
> (http://zguide.zeromq.org/page:all), t
Hi,
What exactly is your test doing? What is your message size and how many
messages you send at a time?
For a test that send one small message at a time between two threads it is
does make sense that IPC message passing would be roughly the same as
inproc transport.
Inproc transport will add a
Hi,
zmsg_ function can be used to send/receive any kind of data in czmq.
http://czmq.zeromq.org/czmq4-0:zmsg
Max
On Wed, May 3, 2017 at 8:53 AM, Brian Sellden wrote:
> Hello,
>
>
>
> I’m using czmq to transfer serialized objects in char arrays. The
> serialized data may contain nulls, so pro
wrote:
> Hi Max,
>
>
>
> I was looking through this a little… If I use zmsg on the receiving end,
> do I have to use zmsgs/zframes on the sending end as well?
>
>
>
> Brian.
>
> *From:* zeromq-dev [mailto:zeromq-dev-boun...@lists.zeromq.org] *On
> Behalf Of *Max K
14 matches
Mail list logo