The default behavior for some input is to send transactions through the server, and wait for the transaction report to flow through the normal data circuit. However, there are cases where you might want to transact locally (for instance, for data that isn't even in the central DB, or for apps which don't even have a central db). And we also want to think about how we control different handler strategies like optimistic update etc. So I think some bit of context data and corresponding control indirection that tells us how a control is supposed to respond to changes would be stellar. Should ideally be flexible, orthogonal to other concerns, etc.
The default behavior for some input is to send transactions through the server, and wait for the transaction report to flow through the normal data circuit. However, there are cases where you might want to transact locally (for instance, for data that isn't even in the central DB, or for apps which don't even have a central db). And we also want to think about how we control different handler strategies like optimistic update etc. So I think some bit of context data and corresponding control indirection that tells us how a control is supposed to respond to changes would be stellar. Should ideally be flexible, orthogonal to other concerns, etc.