ISSUE-12: Determine appropriate size limit for beacon data based on current usage patterns
beacon-size-limit
Determine appropriate size limit for beacon data based on current usage patterns
- State:
- CLOSED
- Product:
- Beacon
- Raised by:
- Jatinder Mann
- Opened on:
- 2014-03-05
- Description:
- Determine appropriate size limit for beacon data based on current usage patterns to help us determine what the right limit should be for beacon data transmissions and whether we should set a limit on number of beacons per page or rate at which beacons are transmitted. Ilya, you had mentioned that you were going to look at Google Analytics data to see what the common analytics package sizes are? That data will go a long way in helping us determine an appropriate limit.
- Related Actions Items:
ACTION-111 on Jatinder Mann to Determine appropriate size limit for beacon data based on current usage patterns - due 2013-11-27, closed- Related emails:
- Re: {minutes} 2014-04-26 Web Performance Working Group: Resource Priorities, HRT2, Beacon, etc. (from arvind@google.com on 2014-04-05)
- {minutes} 2014-04-26 Web Performance Working Group: Resource Priorities, HRT2, Beacon, etc. (from plh@w3.org on 2014-03-26)
- Re: [agenda] Web Performance WG Teleconference #129 Agenda 2014-03-26 (from plh@w3.org on 2014-03-26)
- ISSUE-12 (beacon-size-limit): Determine appropriate size limit for beacon data based on current usage patterns [Beacon] (from sysbot+tracker@w3.org on 2014-03-05)
Related notes:
We had reached consensus to return an error synchronously if size/queue limits are exceeded and not specify an explicit size limit.
See this thread for discussion:
http://lists.w3.org/Archives/Public/public-web-perf/2013Dec/0062.html
Display change log
