[zeromq-dev] What pattern of ZeroMQ best to use for Relay server scenario?

[giedrius.lukosevicius at advantes.tech]

As I understand SERVER - CLIENT pattern requires static IP for each SERVER,
in my case this would be a problem as this should be dynamic (didn't mention
before). Also REP/REQ isn't asynchorous

Any other options?

 

 

From: zeromq-dev <zeromq-dev-bounces at lists.zeromq.org> On Behalf Of B?ch
Ho?ng Nguy?n
Sent: Monday, April 1, 2019 9:09 AM
To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Subject: Re: [zeromq-dev] What pattern of ZeroMQ best to use for Relay
server scenario?

 

For now, only "SERVER" and "CLIENT" socket types is fit to your question.
"SERVER" socket give you routing id, which identify client id.

 

But SERVER and CLIENT still in draft api.

______

Bach Hoang Nguyen (Mr.) - Software Engineer

Email: hoangbach.bk at gmail.com <mailto:hoangbach.bk at gmail.com> 

Mobile: +84973101196

Skype: bachden_hut

 

 





On Mar 31, 2019, at 10:23 PM, giedrius.lukosevicius at advantes.tech
<mailto:giedrius.lukosevicius at advantes.tech>  wrote:

 

What pattern of ZeroMQ best to use for Relay server scenario?

Problem solving:

1.      There are many requestors/clients ( A,B,C )

2.      There are many external servers workers ( X,Y,Z )

3.      Need to set Relay server to serve requests from clients, forward it
to specific worker (e.g. A->X,B->Y,C->Z), get respose from worker and
forward it back to requestor/client.

4.      Relay server autorizes clients and then knows which server needs to
send request by it's name.

 

My first impression was Marjodomo pattern , but not sure how to identify and
keep track on specific worker..

Please suggest!

 

_______________________________________________
zeromq-dev mailing list
 <mailto:zeromq-dev at lists.zeromq.org> zeromq-dev at lists.zeromq.org
 <https://lists.zeromq.org/mailman/listinfo/zeromq-dev>
https://lists.zeromq.org/mailman/listinfo/zeromq-dev

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20190401/fdeb113d/attachment.htm>