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

Support for Sessions #10

Open
drub0y opened this issue Jun 2, 2016 · 0 comments
Open

Support for Sessions #10

drub0y opened this issue Jun 2, 2016 · 0 comments

Comments

@drub0y
Copy link
Owner

drub0y commented Jun 2, 2016

Need to come up with a configuration method for indicating that sessions should be used to receive messages. Basic implementation would simply accept each session and iterate through all of its available messages before moving on to the next session. While this would work, it does not necessarily provide all the possible benefits of having sessions.

Should consider whether the fact that sessions are being used should be surfaced in the API by switching the result type to something like IObservable<IObservable<TMessage>> where each of the values emitted is an IObservable representing the messages within a session. Doing so would allow application logic to partition its work in terms of concurrency amongst sessions, but I'm not sure if the core Obvs [Configuration] API lends itself to presenting this kind of representation.

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