[zeromq-dev] Discard old messages on XPUB before transmission

Daniel Krikun krikun.daniel at gmail.com
Mon Jul 22 11:27:14 CEST 2013


Hello,

This is not exactly the same but might be helpful, I'm working on the
following feature: dependent on a socket option, all messages but the very
last are discarded at the receiver (only PULL, DEALER and SUB socket types).

This is implemented using double buffer instead of queue.


On Fri, Jul 19, 2013 at 3:10 AM, Cem Karan <cfkaran2 at gmail.com> wrote:

>
> On Jul 18, 2013, at 7:07 PM, Steven McCoy wrote:
>
> > On 18 July 2013 16:12, Diego Duclos <diego.duclos at gmail.com> wrote:
> >> I would have use for some of this stuff as well.
> >> However, I don't think it really feels at home in zmq itself ? What
> about a middleware layer between zmq and user apps that takes care of this ?
> >
> >
> > There is a cost on the send side, you would probably want to implement a
> watermark a factor of the network latency and desired lifetime and still
> gain some benefit from network batching.
> >
> > It is technically feasible with PGM to kill the messages in the transmit
> window such that NAKs will be denied and late joiners will not ask for them.
>
> I second Steve; this is something that is best inside of ZMQ as ZMQ really
> knows when it is about to send a message out.
>
> Killing the messages in the transmit window is EXACTLY what I was thinking
> about!  Steve, would this be easy to implement in OpenPGM?  I'm willing to
> look at this, but since I don't know the codebase, I'm not sure where to
> start.
>
> Thanks,
> Cem Karan
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>


-- 
Daniel Krikun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20130722/1607db6e/attachment.htm>


More information about the zeromq-dev mailing list