You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.
The main goal of this issue is to enhance the Blazor and BlazorMobile workflow in order to:
Add a remotly controlled update workflow of an app
Managed totally or partially by the PWA app format
Make the workflow transparent.
Requirement:
Application update workflow must be ATOMIC - The app must be downloaded completely before updating current revision
Application PWA app package must be valided with a checksum from the source server
Get a minimal offline working app in app even if there is not Internet for downloading updates (by Design)
Question:
Can we use a regular compliant PWA technical scenario ? Like using remote server URL as launching URI instead of 127.0.0.1 internally ?
If yes, is there any mecanism to cache another version of the app before updating as we want a minimal app available without internet.
If no to previous questions, we may use the current app package format and executing locally the app, with some addition for validating the PWA app in the workflow.
Notes:
If all ressources are availables and identified from Blazor PWA manifest we may try to download and validate the PWA app without any change to the server. This also mean the PWA app can be hosted on any various kind of server
Otherwise, we may develop a ASP.NET Core extension, but it would make this functionnality less more universal.
The text was updated successfully, but these errors were encountered:
The main goal of this issue is to enhance the Blazor and BlazorMobile workflow in order to:
Requirement:
Question:
Notes:
The text was updated successfully, but these errors were encountered: