Right now we are using selfHref to store the current progression in local storage, but that creates quite a strong dependency on this self href not ever changing.
Now, the path to manifest in CLI has changed with an extra /webpub/ in version 0.6.0 (readium/cli#79), which means that self href has effectively changed for all existing publications, and the progression will never be retrieved nor updated again – in practice it is another key entirely.
This is worrying in the long term, as progression but also the local store for settings could be impacted quite heavily following a server update – and we don't have any syncing to a server in place, we are relying entirely on the client-side ATM.
It is worth keeping this in mind for JWT as well, as things will have to change anyway.
Right now we are using
selfHrefto store the current progression in local storage, but that creates quite a strong dependency on this self href not ever changing.Now, the path to manifest in CLI has changed with an extra
/webpub/in version0.6.0(readium/cli#79), which means that self href has effectively changed for all existing publications, and the progression will never be retrieved nor updated again – in practice it is another key entirely.This is worrying in the long term, as progression but also the local store for settings could be impacted quite heavily following a server update – and we don't have any syncing to a server in place, we are relying entirely on the client-side ATM.
It is worth keeping this in mind for JWT as well, as things will have to change anyway.