> I think this would fall over more often than not. > > Most developers will not write their code to be resilient in the face > of being suspended for extended periods of time. Upon reopening they > would likely display error dialogs, or updated version of whatever was > saved. > > In fact, I would argue that it's directly harmful to keep even some of > the app logic working. It could cause things like overwriting server > state with whatever state was serialized into the saved copy. > > The usecase here isn't to magically make apps available offline. > That's unlikely to ever work well enough that it's worth doing without > author cooperation. The use case here is the ability to save some > *information* for later access. > > If I'm about to leave house to visit a friend, i'm interested in > saving the directions for getting to that friend. I'm less interested > in having an updated facebook feed with me. > > / Jonas
The Service Worker spec addresses various offline use cases quite well. http://www.w3.org/TR/2015/WD-service-workers-20150205/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
