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

CO connection/heap coelescing #38

Open
eswdd opened this issue Nov 1, 2013 · 0 comments
Open

CO connection/heap coelescing #38

eswdd opened this issue Nov 1, 2013 · 0 comments

Comments

@eswdd
Copy link
Contributor

eswdd commented Nov 1, 2013

We want to add the capability such that a client can choose to migrate a subscription to a particular heap uri to a different server. This situation might occur if a request to subscribe comes in, the uri returned by the server matches one that another server has already returned, and so the client would prefer to receive and process only one stream of updates rather than many copies of the same thing.

We would probably want to do this as part of the subscription process, and should be toggleable.

It's also likely that the client would want to be able to direct the initial subscription request to the same server where the parameters (or a certain subset of parameters) for a particular CO method match previous requests - essentially some kind of subscription request to server affinity.

@eswdd eswdd modified the milestones: Release 3.2 Candidates, Release 3.1 Candidates Apr 9, 2014
@eswdd eswdd added the accepted label Jun 26, 2014
@eswdd eswdd removed this from the Release 3.2 Candidates milestone Jun 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant