hi Pieter, > What you probably want to make, what most developers end up making, is > a framework that does the messaging you need (using ZeroMQ) and hides > this from your application. 100% true. This is what I'm doing. In java.
> A TTL is hugely application dependent. Putting this into ZeroMQ would be dramatically bad for most applications. Yes, true, TTL is abstract thing. But, with high probability, everyone would want this: "I want a setting of how long message lives in sending _and/or_ receiving queue". Actually, TTL, in that form which I described above, is "already there". Implicitly, TTL is equal to a life of an in-mem queue. And entire point -- is to allow defining TTL explicitly. What do you think? 2013/12/29 Pieter Hintjens <[email protected]> > On Sun, Dec 29, 2013 at 11:13 AM, artemv zmq <[email protected]> wrote: > > > I can implement TTL myself, making it being as a part of message, _but_ > I > > don't want to do that, because, TTL is low level thing, so fixing it at > > higher level would bring more problems, I suppose. > > Do you know, or do you suppose? If you know, please explain what those > problems are. If you suppose, please try it and let us know whether > there are problems or not. > > Let me explain this another way. A TTL is hugely application > dependent. Putting this into ZeroMQ would be dramatically bad for most > applications. > > What you probably want to make, what most developers end up making, is > a framework that does the messaging you need (using ZeroMQ) and hides > this from your application. ZeroMQ is not that framework and it will > not ever be. > > -Pieter > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
