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

[DHT] value pagination #71

Closed
sim590 opened this issue May 28, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@sim590
Copy link
Contributor

commented May 28, 2016

A logical enhancement after #43 is to introduce pagination of the values. This will let reduce packet size of responses to get requests. The following diagram shows the sequences of a get operation:

sequence diagram

where

  • the SQL-ish statements are describing a query.
  • <q.fields> and <q.filters> respectively denote the fields list and the filters specified by the query the user passed through the API.
  • the id_n are the ids recovered by the first query. n depends obviously on the response to the first request.

@aberaud: what do you think?

@sim590 sim590 self-assigned this May 28, 2016

@sim590

This comment has been minimized.

Copy link
Contributor Author

commented May 30, 2016

I've started to work on this here.

I think that we could also mention an important enhancement to the Dht::put function to be added which is to use the strategy to first get with a SELECT id query and announcing the value only if not already present. This will also be taken care of.

  • value pagination;
  • Dht::put optimization;
@kaldoran

This comment has been minimized.

Copy link
Collaborator

commented Jul 12, 2016

I think this is ended with the merge of #79
Edit : Fail, close wrong one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.