Project:
| View Revisions: Issue #39260 | [ Back to Issue ] | ||
| Summary | 0039260: Send delta age in ping, check delta before going offline | ||
| Revision | 2018-09-25 13:49 by mtaal | ||
| Steps To Reproduce | Run multi-server Simulate offline/online and max age To test the change: - set the new preference to a 1 minute or so - force a sync error (by creating a unit 'c1' in the store and then in central - wait a few minutes - then stop the central server - the webpos will not go offline as the delta age is too old Additional test - force the offline by changing the status in the database directly in the store server - notice that the system reports an illegal offline mode and shows a message |
||
| Revision | 2018-09-25 13:46 by mtaal | ||
| Steps To Reproduce | Run multi-server Simulate offline/online and max age |
||
| Revision | 2018-09-24 21:48 by mtaal | ||
| Description | When sending the ping from cs to ss also send the delta age. Store it in the mobile server definition. When going offline determine if the offline state is valid by checking the age of the delta. Make this age limit configurable, default to 5 minutes. If the delta is old then treat the situation the same as with a sync error: invalid offline which is shown to the user. There is a risk that the store can not go offline after that as the delta is too large. So we will introduce a check procedure which checks the age of the batches in CS. If it is too old we do not allow going offline or transition to online. |
||
| Revision | 2018-09-11 17:54 by mtaal | ||
| Description | When the SS starts currently it starts in offline mode. It seems better to start in the same mode as it was stopped. As this is what it would have been anyway hadn't it stopped. When sending the ping from cs to ss also send the delta age. Store it in the mobile server definition. When going offline determine if the offline state is valid by checking the age of the delta. Make this age limit configurable, default to 5 minutes. If the delta is old then treat the situation the same as with a sync error: invalid offline which is shown to the user. There is a risk that the store can not go offline after that as the delta is too large. So we will introduce a check procedure which checks the age of the batches in CS. If it is too old we do not allow going offline or transition to online. |
||
| Revision | 2018-09-11 09:12 by mtaal | ||
| Description | Allow going online also if there is a large delta. This because it is better if the store can go online than stay offline. This to give the store time to recover. There is a risk that the store can not go offline after that as the delta is too large. So we will introduce a check procedure which checks the age of the batches in CS. If it is too old we do not allow going offline or transition to online. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |