Skip to content
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

callService shouldn't need a previous established connection to call services #79

Open
hughjfchen opened this issue Oct 24, 2019 · 1 comment

Comments

@hughjfchen
Copy link

Currently, before you can use callService/callService' to call services on other nodes, you must use connection, listen or initNode established some connection state. This restrict should be removed because callService/callService' know how to connect to the node where the services it wants to call located.

@agocorona
Copy link
Collaborator

in the meantime, runCloud callService... work fine to call services under the TranIO monad.

callService is asynchronous, so it will execute alternative computations. If that is not desired, use sync . runCloud $ callservice..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants