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

protocol v2 #16

Open
wants to merge 1 commit into
base: protocol_v2
Choose a base branch
from
Open

protocol v2 #16

wants to merge 1 commit into from

Conversation

odobroiu
Copy link

@odobroiu odobroiu commented Feb 2, 2015

Squashed commits and closed previous pr

@odobroiu
Copy link
Author

odobroiu commented Feb 2, 2015

In the last couple of days I have looked into the datastax java driver and have started to think about having the same cluster/session_manager/ approach here.

Currently I have started working on the seestar_cluster, changed the api of seestar_session to export less methods and added events decoding. Changes can be seen here https://github.com/odobroiu/seestar/tree/seestar_cluster .

Also tried out some things for the having some sort of session manager, but decided to give that up as it was mostly exploring. From my point of view there are 2 approaches for something similar to the session manager:

  1. Have a session_manager module that can return a session pid, that the client would use. This is the path I was exploring, but came to the conclusion that at least the encoding of requests should be moved inside the session process so that we could notify the session manager pid to prepare the query on all the other hosts.
  2. Proxy the seestar_session. All the requests sent to the seestar_manager would be sent async to the seestar_session, and the seestar_session would reply directly to the process that calls seestar_manager. However, the encoding part would still have to be done inside this process for the same reason of having the prepared queries executed on all hosts( At least that is my current view on this issue, might not be 100% true).

Either way, if you think the seestar_cluster branch is useful ( mostly if you like the api of the seestar session better), I could document and clean it up in the next 24-48 hours and create a pr.

Will be on holiday feb 4th - feb 20th, but afterwards if you'd like we could talk about having similar functionality to the java driver.

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

Successfully merging this pull request may close these issues.

1 participant