From 200e255820ac897440705a2c702b417e0fc67972 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 7 May 2020 00:11:06 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 39d06e8d..aa1a537a 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -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) * 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 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