Nikhil Marathe [:nsm] (No longer reading bugmail, please needinfo?) Assignee
	Description • 10 years ago

The fetch() function is available on ServiceWorkerGlobalScope, and asks the UA to make a HTTP request on the ServiceWorker's behalf according to the Fetch specification.

Filing in Necko since most of the work will be exposing Fetch spec semantics via existing HTTP infrastructure.

Relevant specs:
Fetch: http://fetch.spec.whatwg.org/
ServiceWorker: http://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html

	Jason Duell
	Comment 1 • 10 years ago

> Filing in Necko since most of the work will be exposing Fetch spec 
> semantics via existing HTTP infrastructure.

This looks more like an XHR-like thing to me (i.e. a bunch of wrapper code around HTTP channels, that doesn't necessarily live in /netwerk).  Jonas, do you have an idea where this code should live?

	Jonas Sicking (:sicking) No longer reading bugmail consistently
	Comment 2 • 10 years ago

The code should probably live in contant/base/src or dom/base.

FWIW I would expect that the implementation would look significantly different from the XHR code since most of the XHR code is back-compat cruft and event handling code, neither of which is needed for the fetch() API.

	Nikhil Marathe [:nsm] (No longer reading bugmail, please needinfo?) Assignee
	Comment 3 • 10 years ago

Taking for now since I have some patches.

	Nikhil Marathe [:nsm] (No longer reading bugmail, please needinfo?) Assignee
	Comment 5 • 10 years ago

Closing as dom-fetch-api deals with all of this.