/pyzor

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

Add support for batching reports to the Pyzor server. #13

Closed
alexkiro opened this Issue Jun 13, 2014 · 0 comments

Comments

Assignees

@alexkiro alexkiro

Labels
Projects
None yet
Milestone
  0.8
1 participant
@alexkiro
@alexkiro
Contributor

alexkiro commented Jun 13, 2014

For long running daemons/operations (such as the new forwarder system), the Pyzor client could be improved to batch the reports (or whitelist) to the server. The server will also need to adjust it's protocol to accept multiple digests.

ISTM that the simplest way to do this is by appending more headers Op-Digest headers to the request.

@alexkiro alexkiro added enhancement labels Jun 13, 2014

@alexkiro alexkiro added this to the 0.8 milestone Jul 11, 2014

@alexkiro alexkiro self-assigned this Jul 11, 2014

alexkiro added a commit that referenced this issue Jul 11, 2014

@alexkiro
Refs. #13. Add support for batched reports. 
Add a new class BatchClient that will send batch send 10 digests to the specified servers. The batches are per server/per operation. Only report and whitelist operations are currently batched. Add support for multiple "Op-Digest" headers in the pyzor server.
cc84ed0

alexkiro added a commit that referenced this issue Jul 11, 2014

@alexkiro
Refs. #13. Add tests for the batched report/whitelist functionality.
Loading status checks…
c3c6672

alexkiro added a commit that referenced this issue Jul 11, 2014

@alexkiro
Refs. #13. Adjust the forwarder feature to use batched reporting. 
The forwarder feature will now send reports and whitelists in batches
of 10 digests per address.
Loading status checks…
fa63720

@alexkiro alexkiro closed this Jul 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment