Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rephrase "Off-line application mode" #9

Open
jlouvel opened this issue May 3, 2013 · 2 comments
Open

Rephrase "Off-line application mode" #9

jlouvel opened this issue May 3, 2013 · 2 comments

Comments

@jlouvel
Copy link
Member

jlouvel commented May 3, 2013

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.

@ghost ghost assigned jlouvel May 3, 2013
@mamund
Copy link

mamund commented May 4, 2013

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?

@jlouvel
Copy link
Member Author

jlouvel commented May 10, 2013

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants