Please read for an updated status on RailsCasts:
Learn more or hide this
GitHub User: Zifro
Metin, I totally agree with your definition of an "offline application", but remember that's a "part 1".
Moreover, it's good to be able to use the application to build up your grocery list while connected (at home, for example) then bring it to the supermarket with you while not connected.
Like Roberto Ruiz, I'm wondering if the issue raised with the manifest file not being invalidated after the database is updated, could not be handled by a sort of cache.
When the database stage changes, we want the application to issue a new manifest file, with a new ID within.
Is that possible or the problem is even bigger ?