I've updated the processing model to refer to the entry settings object per Ian's latest comment. https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/Beacon/Overview.html#sec-processing-model Please let me know if this looks ok. Arvind On Wed, Feb 12, 2014 at 4:44 PM, Richard Barnes <rbarnes@mozilla.com> wrote: > On 2/12/14, 6:33 PM, Jonas Sicking wrote: > >> On Wed, Feb 12, 2014 at 3:02 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: >> >>> On 2/12/14 5:52 PM, Jonas Sicking wrote: >>> >>>> >>>> I personally think C makes the most sense since it doesn't involve >>>> grabbing some omnious global state. Instead the behavior is determined >>>> by the more tangible answer to the question "which object did you call >>>> a function on". >>>> >>> >>> What object, or what function? >>> >>> Consider windowC.navigator.sendBeacon.apply(windowD.navigator, args) >>> >> >> I would say D here. Carrying state in functions feels a lot more hacky >> than carrying state in objects. >> > > That was my reaction as well. > > --Richard > > > >> / Jonas >> >>
Received on Thursday, 13 February 2014 05:58:04 UTC