Service Workers in Construct 2

0 favourites
  • 2 posts
From the Asset Store
Casino? money? who knows? but the target is the same!
  • why construct 2 uses service workers fetch event like this

    self.addEventListener("fetch", event =>
    	/** NOTE (iain)
    	 * This check is to prevent a bug with XMLHttpRequest where if its
    	 * proxied with "FetchEvent.prototype.respondWith" no upload progress
    	 * events are triggered. By returning we allow the default action to
    	 * occur instead. Currently all cross-origin requests fall back to default.
    	if (new URL(event.request.url).origin !== location.origin)
    	// Check for an update on navigate requests
    	const doUpdateCheck = (event.request.mode === "navigate");
    	const responsePromise = HandleFetch(event, doUpdateCheck);
    	if (doUpdateCheck)
    		// allow the main request to complete, then check for updates
    			.then(() => UpdateCheck(false))		 // not first check
    self.addEventListener('fetch', event => {
     if (event.request.mode === 'navigate') {
     // See /web/fundamentals/getting-started/primers/async-functions
     // for an async/await primer.
     event.respondWith(async function() {
     // Optional: Normalize the incoming URL by removing query parameters.
     // Instead of,
     // use when reading and writing to the cache.
     // For static HTML documents, it's unlikely your query parameters will
     // affect the HTML returned. But if you do use query parameters that
     // uniquely determine your HTML, modify this code to retain them.
     const normalizedUrl = new URL(event.request.url); = '';
     // Create promises for both the network response,
     // and a copy of the response that can be used in the cache.
     const fetchResponseP = fetch(normalizedUrl);
     const fetchResponseCloneP = fetchResponseP.then(r => r.clone());
     // event.waitUntil() ensures that the service worker is kept alive
     // long enough to complete the cache update.
     event.waitUntil(async function() {
     const cache = await'my-cache-name');
     await cache.put(normalizedUrl, await fetchResponseCloneP);
     // Prefer the cached response, falling back to the fetch response.
     return (await caches.match(normalizedUrl)) || fetchResponseP;
  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Do you have a specific question? If you are just asking "why didn't you write a completely different function", the answer is "because it works differently".

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)