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
A Server class allows to expose only a single Service (rpyc.utils.server.Server(service,..)
I suppose that with a Service- and ZeroDeploy-based approach it would be much better and more flexible to allow multiple Services to be exposed by a single remote Server within a single Connection.
I am using the RPyC for remote testing and I have multiple remote resources abstracted as separate Services. I want multiple Services to be accessible from a given single remote machine without the need to create multiple remote Server instances, as my machines are usually already under significant load.
I can try implementing the idea, are there any obvious architectural/design contraindications?
The text was updated successfully, but these errors were encountered:
Currently:
rpyc.utils.server.Server(service,..
)I suppose that with a Service- and ZeroDeploy-based approach it would be much better and more flexible to allow multiple Services to be exposed by a single remote Server within a single Connection.
I am using the RPyC for remote testing and I have multiple remote resources abstracted as separate Services. I want multiple Services to be accessible from a given single remote machine without the need to create multiple remote Server instances, as my machines are usually already under significant load.
I can try implementing the idea, are there any obvious architectural/design contraindications?
The text was updated successfully, but these errors were encountered: