systemXHR is the one I bang on about specifically due to offline, I havent finished my experiments with serviceWorkers but between seeing every other developer get confused due to CORS using pouchdb and my (and others https://gauntface.com/blog/2015/02/11/fetch-is-the-new-xhr) initial confusion with opaque responses to fetch + serviceWorkers I can only see it being increasingly hard to build offline applications without the ability to control and read remote data.
On 18 February 2015 at 12:02, Anne van Kesteren <[email protected]> wrote: > On Wed, Feb 18, 2015 at 12:51 PM, Anne van Kesteren <[email protected]> > wrote: > > Trying to figure out how to get sockets and "systemXHR" into the > > browser has been going on for a very long time now, I think we should > > start embracing that it's unlikely to happen and look elsewhere. > > Also, if you look at where our focus should be in terms of APIs, this > does not seem like it is it: > > https://tctechcrunch2011.files.wordpress.com/2014/08/13.jpg > > Looking through that list, these things come to mind: > > * Offline > * WebRTC, including video and microphone input > * Camera > * Media Keys > > And performance of course... > > > -- > https://annevankesteren.nl/ >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
