[zeromq-dev] Which ZMQ Messaging Pattern to use?

Matteo matteo.brichese at gmail.com
Fri Dec 14 21:37:15 CET 2018


Hi,

i believe pub/sub is the best approach.
The publisher holds all the logic on sending based on time.

At the end of the pubblication the pub could send a termination message and
shutdown if necessary.

Does it make sense?
What was holding you?

Regards


On Fri, Dec 14, 2018 at 14:31 codyq0987 <askmatlab at gmail.com> wrote:

> Hello all,
>
> I have an application that keeps computing stream data from T1(i.e 8:00
> AM) to T2(i.e. 10:00 AM). I want to utilize the pyzmq to serve the data to
> clients by building a data service based on ZMQ.
>
> Here is the user cases:
>
> For example,
> Case 1> if a client connects to the server @8:10 AM, the server will send
> all old data before 8:10 AM and all new updates to the client. The client
> will get data based on the submitted topic.
>
> Case 2> If the client connects to the server @7:00 AM, the server simply
> does nothing and will send updates to the client after 8:00AM and close the
> connection @10:00AM.
>
> Case 3> If the client connects to the server @11:00 AM, the server will
> send all available data from 8:00AM-10:00AM to the client and then close
> the connection.
>
> Note: if two clients connect to the server, each of them will get the full
> data starting from 8:00AM.
>
> Based on my understanding, I cannot find any of the standard message
> patter that is suitable for this purpose.
>
> PAIR
> Client/Server
> Publish/Subscribe
> Push/Pull
>
> Question> In my use case, how I should implement the client/server with
> ZMQ and which messaging pattern I should use?
>
> Thank you
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-- 
Sent from iPhone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20181214/5755405d/attachment.htm>


More information about the zeromq-dev mailing list