[Bug 42815] Provide a robust way of logging events without blocking until network request completes; use sendBeacon with client-side storage fallback
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 --- Comment #13 from Gerrit Notification Bot gerritad...@wikimedia.org --- Change 162194 had a related patch set uploaded by Prtksxna: Add an experimental function to log events using the sendBeacon API. https://gerrit.wikimedia.org/r/162194 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 42815] Provide a robust way of logging events without blocking until network request completes; use sendBeacon with client-side storage fallback
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 Gerrit Notification Bot gerritad...@wikimedia.org changed: What|Removed |Added Status|REOPENED|PATCH_TO_REVIEW -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 42815] Provide a robust way of logging events without blocking until network request completes; use sendBeacon with client-side storage fallback
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 Matthew Flaschen mflasc...@wikimedia.org changed: What|Removed |Added Depends on||64721 Summary|Provide a robust way of |Provide a robust way of |logging events without |logging events without |blocking until network |blocking until network |request completes |request completes; use ||sendBeacon with client-side ||storage fallback --- Comment #12 from Matthew Flaschen mflasc...@wikimedia.org --- (In reply to Krinkle from comment #11) Firefox landed it recently in stable: https://developer.mozilla.org/en-US/docs/Web/API/navigator.sendBeacon https://developer.mozilla.org/en-US/Firefox/Releases/31 Chrome landed it in canary (Chrome 37), soon to be in stable: https://code.google.com/p/chromium/issues/detail?id=360603 This seems like a good choice then. We can use sendBeacon when available, and use jStorage when it's not. However, ideally, the issue with localStorage being used up should be solved first, or the fallback will be less effective (or have to use cookies). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 42815] Provide a robust way of logging events without blocking until network request completes
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 Krinkle krinklem...@gmail.com changed: What|Removed |Added CC||krinklem...@gmail.com --- Comment #11 from Krinkle krinklem...@gmail.com --- (In reply to Ori Livneh from comment #7) The Beacon API proposal from the W3C Web Performance Working Group, published last month, takes a stab at solving the exact problem that this bug describes: https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/Beacon/Overview.html The proposal itself is just that -- a proposal. I don't think any browser vendors implement it yet. Firefox landed it recently in stable: https://developer.mozilla.org/en-US/docs/Web/API/navigator.sendBeacon https://developer.mozilla.org/en-US/Firefox/Releases/31 Chrome landed it in canary (Chrome 37), soon to be in stable: https://code.google.com/p/chromium/issues/detail?id=360603 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 42815] Provide a robust way of logging events without blocking until network request completes
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 Tisza Gergő gti...@wikimedia.org changed: What|Removed |Added Blocks||56426 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 42815] Provide a robust way of logging events without blocking until network request completes
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 Matthew Flaschen mflasc...@wikimedia.org changed: What|Removed |Added CC||aaron.halfa...@gmail.com, ||samsm...@wikimedia.org Summary|Provide a robust way of |Provide a robust way of |synchronously logging |logging events without |events |blocking until network ||request completes --- Comment #9 from Matthew Flaschen mflasc...@wikimedia.org --- Bumping the priority on this and renaming somewhat, since this seems to be the preferred approach (for performance reasons) for moving forward on the link click problem. See discussion at https://bugzilla.wikimedia.org/show_bug.cgi?id=52287 . I propose using jQuery jStorage, which is a localStorage wrapper (already in core) with support for globalStorage and IE userData as a fallback. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 42815] Provide a robust way of logging events without blocking until network request completes
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 Matthew Flaschen mflasc...@wikimedia.org changed: What|Removed |Added Priority|Low |High -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 42815] Provide a robust way of logging events without blocking until network request completes
https://bugzilla.wikimedia.org/show_bug.cgi?id=42815 --- Comment #10 from Matthew Flaschen mflasc...@wikimedia.org --- (In reply to Matthew Flaschen from comment #9) I propose using jQuery jStorage, which is a localStorage wrapper (already in core) with support for globalStorage and IE userData as a fallback. To be clearer, jStorage has support for globalStorage and userData too. We wouldn't need to add that. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
