You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggested by Robert Brewer: I would rephrase it to "disconnected operation" and make it a constraint.
That constraint plus the cache constraint could lead to an architecure which syncs caches on reconnection, but that design decision is not part of the style.
The text was updated successfully, but these errors were encountered:
how is this different than the cache constraint? what else is in this "disconnected operation" thing? and why is this a constraint and not a requirement?
If you think about how Git is working with local commits, I think this could illustrate how far we might go in the end regarding a disconnected API mode.
OData is an illustration of a rather RESTful web API that has support of batch operations that comes rather close to what I have in mind
Suggested by Robert Brewer: I would rephrase it to "disconnected operation" and make it a constraint.
That constraint plus the cache constraint could lead to an architecure which syncs caches on reconnection, but that design decision is not part of the style.
The text was updated successfully, but these errors were encountered: