On 08/14/2012 06:32 AM, Robert Kaiser wrote:
Anant Narayanan schrieb:
Updating packaged apps is a reasonably well-understood problem, hosted
Apps on the other hand are a bit more complicated.
Actually, for me, hosted apps feel well-understood as they (should)
follow the web paradigm of not having versioned updates but rather TTL,
just like websites do. There's some kind of cache, the contents of it
have a TTL, after that, current contents get renewed from the origin
(or, more elaborate, the origin is asked if the current content differs
from the cached content and the cache is only refreshed if so) and the
TTL "timer" starts anew. If you want to be able to avoid more edge cases
of that model, you can enable the app/site to trigger an early,
"unscheduled" cache eviction/refresh.
That's what I would expect from hosted apps, as it's the "webby" model.
The fundamental problem we are dealing with is that while the
application itself is not versioned (just like web pages), the manifest
that describes an application is a static file. While the manifest may
be updated at any time by the developer, certain changes cannot be
transparently applied.
I actually find updating of packaged apps much less understood from my
POV, as anything I can think of feels so un-webby and is another thing
that increases the rift between the "webby" model I just described and
the "not-of-the-web" packaged model. ;-)
I agree that packaged apps are not webby, however they are well
understood in the sense that all other app stores use this model (iOS,
Android and now even the Chrome store) and that updating a static set of
resources in a zip file is less complex than attempting to "version" a
live resource like a web application.
-Anant
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
