-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discovery between different process #5
Comments
Currently services are registered into a manager from there : https://github.com/asmodehn/pyzmp/blob/master/pyzmp/service.py#L30 so discovery is very simple in one interpreter... We need to improve that... |
The properway to do that is likely to store our node details in |
Note : for authorization we need to rely on process authorization from OS, and not implement our own on top of it (or nightmare will ensue...) |
Also relates to #8 |
TODO : Deep dive into : https://www.gitbook.com/book/gritzko/swarm-the-protocol/details |
Idea is to implement something similar to SWARM, in python, but at a slightly lower level... Maybe something around python pickled named tuples... |
It seems we need first to implement something much simpler, for a start : #26 |
We should ultimately rely on colos for the "machine-local" discovery (identifying compatible coprocesses locally) But as we move into the pyzmp layer, with network enabled, some distributed storage seems necessary to implement service discovery across multiple machine, that is multiple instances of colos. |
Refer to https://github.com/asmodehn/pyzmp/blob/docs/docs/tutorial.rst
We need to have a way to do service discovery on a system, even if the different process have been generated previously, from different interpreters...
While direct addressing the process using the zmp socket URL is probably trivial enough, we need to design some system to be able to connect to a set of processes and discover services, without previous knowledge of the system...
The text was updated successfully, but these errors were encountered: