You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am interested in using the Client-Server pattern (https://zeromq.org/socket-api/) in my rust project, so just wanted to register that interest here and add these socket types to the list of issues for implementing others.
The text was updated successfully, but these errors were encountered:
Hi, I want a single central server that gets "jobs" submitted from clients, the channel back to the client has an ID that the server stores in the job and uses to send updates to that client as the job is processed (seconds or minutes to complete).
The server is multi threaded/async and able to process multiple jobs in parallel, so it needs a unique channel (via ID?) back to the client that submitted it.
It needs to be able to accept new jobs at any time, from any new client.
With REQ/REP (I have implemented) there is a pair of "channels" so server can just reply to the one client AFAIK.
When reading the docs, it sounded like the experimental client-server model fitted those needs.
I am interested in using the Client-Server pattern (https://zeromq.org/socket-api/) in my rust project, so just wanted to register that interest here and add these socket types to the list of issues for implementing others.
The text was updated successfully, but these errors were encountered: