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

Concurrency models to support with native language bindings #52

Open
jrhea opened this issue Dec 19, 2018 · 0 comments
Open

Concurrency models to support with native language bindings #52

jrhea opened this issue Dec 19, 2018 · 0 comments

Comments

@jrhea
Copy link

jrhea commented Dec 19, 2018

Opening this issue to continue the discussion we started regarding what concurrency models that should be supported when targeting language level bindings.

Asynchronous Model

Concurrency handled on the Go client side. Async calls from Java/Python/C etc that require a response are tracked with an id. There are two ways we could handle this:
1) Java/Python/C could poll the Go client until the matching response id is returned
2) Java/Python/C could provide a function pointer and the Go client could issue a callback when the response is ready.

I prefer option 2 here

Synchronous Model

There might be cases where we want to provide a synchronous mode of interaction. This might be useful for simulations where we want things to happen during each timestep for the purpose of research and reporting the health of the network given different simulated pathological scenarios.

Just a thought. I am curious what you guys think

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

1 participant