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

outputs/statink: Retry POST to stat.ink in case of any communication errors. #134

Open
hasegaw opened this issue Mar 5, 2016 · 1 comment

Comments

@hasegaw
Copy link
Owner

hasegaw commented Mar 5, 2016

  1. Save the stat.ink payload if the submission failed.
  2. Retry POST later, and delete the file if the submission is successiful.

The change should expand stat.ink maintenance window, and minimize number of game results beinng leaked in stat.ink.

@hasegaw
Copy link
Owner Author

hasegaw commented Mar 5, 2016

Possible situations:

  • stat.ink processed the post, and HTTP request completed successfully
  • stat.ink processed the post, but HTTP request didn't complete, that IkaLog should retry.
  • stat.ink returned permanent error(s) that IkaLog shouldn't retry.
  • stat.ink is unresponsive that IkaLog should retry.

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