Subscriber binding a socket instead of connecting (client vs server) ?

Hello @dashersw

Following development of the c-cote library, I notice that the Publisher is always a "server", which means it is binding a socket, while the Subscriber is always a "client", connecting to discovered server.

I think user can benefit of the opposite too: a Subscriber "server", binding a socket and waiting for Publisher "clients" to send data.

Is it something that was studied ? wanted maybe by other people ?

This can be the beginning of a discussion on the subject if you want. This is still something handle by Axon but just need to be used in cote if we want it.

Joel

PS : I though about Requester and Responder but not sure it is a real use case to have Requester binding a socket and Responder connecting to clients...