admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2020-05-07 00:11:06 +00:00
parent 77f37a4ce3
commit 200e255820
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
ayanova/devdocs/todo.txt
View File

@@ -118,7 +118,11 @@ todo: PLANNING WORKORDER considerations:
how to update client end with update back from server when saved (server will add id and may change fields or even add things) how to update client end with update back from server when saved (server will add id and may change fields or even add things)
* TONS OF ROUTES: Update individual portions as seperate objects to their own routes sequentially * TONS OF ROUTES: Update individual portions as seperate objects to their own routes sequentially
i.e. client determines what's different, only sends an update for each object to it's own route i.e. client traverses and diffs virgin copy and edited copy of wo
determines what's different, only sends an update for each object to it's own route as appropriate
on successful update fixes up the edited copy of that object
on all updates done, the edited copy becomes the virgin copy (or do we need 3 objects at one point in case of fail?)
requires second copy of wo for diffing requires second copy of wo for diffing
goes over workorder, looks for changes, sends update for each object individually and patches up local from result goes over workorder, looks for changes, sends update for each object individually and patches up local from result
so if a workorderitempart has changed then it sends only that for update individually so if a workorderitempart has changed then it sends only that for update individually