You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: