Raising issue per action 01 of CG meeting on Jun 17, where we discussed the issue w3c/miniapp-lifecycle#8 (Update mechanism of MiniApps).
Apart from the possible effects in terms of lifecycle (i.e., trigger events, change status) we commented that the update mechanisms of MiniApps might affect mainly the Packaging and Manifest specs.
The MiniApp Packaging spec includes an algorithm for fetching and processing the package. So, the update mechanism may affect this algorithm. So far, the user agent fetches the package and process it once. Should we include additional metadata (in the Manifest?) to indicate how/when to update the package?
The current package processing algorithm would finish when the MiniApp reaches the launched status, so we could extend the algorithm to update the package once the MiniApp is launched.
Comments?
Raising issue per action 01 of CG meeting on Jun 17, where we discussed the issue w3c/miniapp-lifecycle#8 (Update mechanism of MiniApps).
Apart from the possible effects in terms of lifecycle (i.e., trigger events, change status) we commented that the update mechanisms of MiniApps might affect mainly the Packaging and Manifest specs.
The MiniApp Packaging spec includes an algorithm for fetching and processing the package. So, the update mechanism may affect this algorithm. So far, the user agent fetches the package and process it once. Should we include additional metadata (in the Manifest?) to indicate how/when to update the package?
The current package processing algorithm would finish when the MiniApp reaches the
launchedstatus, so we could extend the algorithm to update the package once the MiniApp is launched.Comments?