This is not complicated, especially being Web system.
All means of environment client have an area of Storage - even browsers. Usually these areas of Storage work simply, with key and value - key value.
Vc can implement something like the following pseudo code:
sendData = (data) => {
_http.send(data,
(response) => { success(response); },
(error) => { _retryStorage.add(data); });
};
So have a service periodically doing something like:
var data = _retryStorage.pop();
data && sendData(data);
So if you haven’t been able to upload the data to the server, play Torage to recover later. So another asynchronous service is "listening" to this line, and if there’s something there, try to re-send.
Remember that this is just a pseudo code, there is much to develop to work as expected, but it is a good way to be followed.
web system... has to be on the internet right... otherwise it has to be a mobile system that saves in a sqlite bank for example... then make the synchronization...
– Rovann Linhalis
You can work with the Indexeddb and synchronize with your remote BD whenever necessary.
– Eduardo Oliveira
@Rovannlinhalis not necessarily. One can easily persist given in the browser’s Storage area. It is a simple, key/value system, but it serves very well.
– Thiago Lunardi
@Rovannlinhalis agree with your statement. I thought of something like ASP.NET Core Self Host to be hosted on the device itself, because I believe the system will be installed on tablets with Android.
– Jr. Pacheco
@It’s also a possibility to do this. But I need the size of the Storage browser not to exceed with the amount of information.
– Jr. Pacheco
@Thiagolunardi’s solution looks good, but it depends on the purpose... I mistakenly thought it was temporary data, but the limitation happens in size: "At least 5MB": https://www.w3schools.com/html/html5_webstorage.asp
– Rovann Linhalis
Anyway, I would go by a compiled application, in Xamarim for example...
– Rovann Linhalis
@Rovannlinhalis I think will be the best.
– Jr. Pacheco