DEPENDENT ON: doozerdev/coreAPI#3 - adding session support for multiple clients.
when that work completes, each client will need to be careful to only update the specific field that the user changed, so that we can reduce the cases of conflicts/data loss across clients.
currently the save item functionality just posts all the properties from the client, regardless of which have changed. this means that the whole item from the client trumps the server copy of the item, and we lose the ability to merge items across clients at the property by property granularity.
DEPENDENT ON: doozerdev/coreAPI#3 - adding session support for multiple clients.
when that work completes, each client will need to be careful to only update the specific field that the user changed, so that we can reduce the cases of conflicts/data loss across clients.
currently the save item functionality just posts all the properties from the client, regardless of which have changed. this means that the whole item from the client trumps the server copy of the item, and we lose the ability to merge items across clients at the property by property granularity.