In the event of a network failure, what technology is used to store local data (ie purchases) in the POS module?
This question is primarily asked to figure out the best practices for what to do during a network access failure for the point of service module. If the network goes down, how well will the POS work? It seems to store purchases locally and then a user is able to validate the purchases once network access is reestablished.
How long will this data persist? How many off network purchases can be performed (how much data can be stored)?
How does a network access failure effect other modules?
The POS module in 7.0 (and probably 6.0 and 6.1) uses LocalStorage, which is a feature supported by most modern browsers that allows the application to store persistent data. This data stays on the computer until either 1) the application deletes it or 2) the user deletes it. So, it is persistent across sessions, reboots, crashes, etc. Most browsers use the browser cache for this data, so unless you delete the cache it should always be available. The size of the LocalStorage is determined by the Browser, but it's usually around 5 MB.
The POS module loads all the data it needs, such as Products, at the beginning of the session, and as you make sales the data is transmitted to the OpenERP server. If you lose connectivity, the data is stored in LocalStorage and the POS will try to resend it periodically. When you regain connectivity the sales data stored in LocalStorage will be transmitted to the OpenERP server.
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 4/1/13, 3:30 PM|
|Seen: 1297 times|
|Last updated: 4/13/15, 2:00 AM|