Pairwise simplify RemoteService-s
@giomasce is already working on this.
Since Jul 10, 2013.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
At the moment, for each pair of services in CMS, there are two open socket (and two corresponding RemoteServices-s in each of the running processes): one is used exclusively in one direction, one only in the other.
Apart from being a bit silly (since sockets are bidirectional), this means that there cannot be "anonymous" services; i.e., services that are not listed in cms.conf. Because for communication to happen it is needed that both services know how to connect each to the other. If services were able to reuse an incoming socket also to send, a "known" service could interact with an "anonymous" service (provided that it is the anonymous one that creates the socket).
I'm pretty sure that allowing "anonymous" services would significantly simplify some aspects of CMS configuration, so would like this issue to be solved.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.