-
Notifications
You must be signed in to change notification settings - Fork 11
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
support for offline mode with queued hit requests #3
Comments
strategy is simple implement a custom if no connection if connection calculation is easy note from the doc
|
we would need 2 timers a global timer that look and send queued requests a timer loop for each queued request |
priority: make it work with AIR eg. AIR have a a easy |
Hi Zwetan, |
yeah been a busy year, it was planed for v0.9 milestone and still is I ll try to release that for the 1st nov 2016 more or less |
Good news! Merci beaucoup ! |
I'm also looking forward to this. |
OK, so I presented the problem wrongly It's not
it's more about
the problem is not "if no connection" do this, but "if the request fail" do that. so to answer your questions
the request fail, if there is an option to queue the request
with a mechanism to queue the requests when they fail nothing should be completely missed as long as the timestamp is not older than 4h, a limitation of the Queue Time parameter Doing it this way should allow to cover both Flash and AIR (and even Redtamarin), avoid the classic problem of polling on a URL to check if there is a connection or not (see Unusual traffic from your computer network), and be able to avoid to track the order of requests. For example, if you send 10 screenviews, but at the time of screenview 6 and 7 the requests failed (internet connection problem, switch from wifi to other, etc.), then the following requests 8, 9 10 pass through, the array of stored failed request would kick-in after that and resend screenview 6 and 7. Because Google Analytics backend register the hit either when it is received or based on the Queue Time parameter, even unordered requests should be able to be register at the right place and time. The goal is to keep it simple, make it not the default behaviour but "user actionable", |
That's amazing! Thanks for your answer! |
see Queue Time parameter
"Used to collect offline / latent hits.
The value represents the time delta (in milliseconds) between
when the hit being reported occurred and the time the hit was sent."
The text was updated successfully, but these errors were encountered: