[zeromq-dev] Feedback on new PATCH socket

[Martin Sustrik]

On 05/06/2011 08:00 PM, Fabien Ninoles wrote:

> AREQ sockets are simple XREP wrappers that add a delimiter on each
> send and remove it on each recv. AREP sockets are simple XREQ
> wrappers that crop and save the address stack of receive messages,
> prepend the last one on each send.
>
> BTW, the last two sockets served me a lot previously, mainly in
> asynchronous context (where the A came from) where I have to keep our
> old worker spanning code instead of ZMQ broker.  With PATCH, however,
> it seems to become a normal pattern, especially AREQ which is
> necessary the moment you need to connect more than one endpoint to a
> PATCH socket.  Could we consider to add it in the standard socket
> types ?

To do the thing properly we have to understand the new messaging pattern 
in detail.

So, as far as I can say, it's basically a census. One socket, let's call 
it SURVEYOR, publishes a form for participants to fill in. It also 
defines a deadline for the census. The participants, let's call them 
RESPONDENT sockets, fill in the form and send it back to the SURVEYOR. 
All the forms received before the deadline are then passed to the user, 
while those that arrive after the deadline are ignored.

Does that kind of model fit your use case?

Martin