Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
In 'Totally Tooling Tips' web developers Matt and Addy discuss the latest topics, issues and work arounds for building apps and libraries to help mop up your Totally Tooling Tears. 
No comment yet.
Sign up to comment
Scoop.it!
JavaScript Fetch API usage examples, how to use fetch() natively in JavaScript
Scoop.it!
When AppCache arrived on the scene it gave us a couple of patterns to make content work offline. If those were the patterns you needed, congratulations, you won the AppCache lottery (the jackpot remains unclaimed), but the rest of us were left huddled in a corner rocking back & forth. With ServiceWorker we gave up trying to solve offline, and gave developers the moving parts to go solve it themselves. It gives you control over caching and how requests are handled. That means you get to create your own patterns. Let's take a look at a few possible patterns in isolation, but in practice you'll likely use many of them in tandem depending on URL & context.
Scoop.it!
Look at the apps on your homescreen. Why are they native? Why aren't they just on the web? Its usually some combination of push messaging, background sync, offline & performance. When native has something the web doesn't, we should consider it a bug. Let's have a look at the fixes,...
|
Scoop.it!
Fetch is a simpler way of getting resources in Javascript compared to XHR. This post is just a brain dump of how to use fetch to make requests. The Fetch API is available in service workers today and in the global space (a.k.a in the normal Chrome window)
Scoop.it!
Service Worker will revolutionize the way we build for the web. Learn about what it is, why it is important and how to use it. Rich offline experiences, periodic background syncs, push notifications— functionality that would normally require a native application—are coming to the web. Service workers provide the technical foundation that all these features will rely on. Contents: * What is a Service Worker?
Scoop.it!
ServiceWorker is a background worker, it gives us a JavaScript context to add features such as push messaging, background sync, geofencing and network control. In terms of network control, it acts like a proxy server sitting on the client, you get to decide what to do on a request-by-request basis. You can use this to make stuff work faster, offline, or build new features. I'm biased, but I think ServiceWorker changes the scope of the web more than any feature since XHR.
|
