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

Skip our freshness ping #2

Open
pjf opened this issue Feb 15, 2013 · 1 comment
Open

Skip our freshness ping #2

pjf opened this issue Feb 15, 2013 · 1 comment

Comments

@pjf
Copy link
Owner

pjf commented Feb 15, 2013

Currently we ping the servers on object creation to see if our session is still fresh. Ideally we could skip this, and try to do a login the first time we call a method that gets back an authorisation error.

This would double the speed of most of the command line scripts.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@pjf
Copy link
Owner Author

pjf commented Feb 19, 2013

Currently we make an HTTP request to see if our session is still fresh. Ideally, we could simply assume our session is fresh, and then refresh it if it's discovered that it's not.

The most straightforward way of doing that is by having a method which is responsible for handling all http requests, which handles the refresh automatically when required, and then re-writing all existing requests to go through that.

Should be a simple matter of code. :)

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