Skip to content
New issue

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

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

Already on GitHub? # to your account

Detail the Custom Interface constraint #10

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

Detail the Custom Interface constraint #10

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

Comments

@jlouvel
Copy link
Member

jlouvel commented May 3, 2013

Suggested by Robert Brewer.

Under "Custom Interface", it would be very informative to lay out in detail which of the properties are being traded off when selecting explicit versioning. Not to evangelize them over REST or vice-versa, but to understand in which situations each is appropriate.

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

mamund commented May 4, 2013

versioning is a technique, not a feature. elevating vesioning to a property/requirement is, IMO, a very bad idea.

@jlouvel
Copy link
Member Author

jlouvel commented May 9, 2013

I agree that versionning is not a feature, it just comes in the blog post to illustrate the Custom Interface constraint and the properties it results in.

This should likely go into an Evaluation section (see related issue #17).

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

No branches or pull requests

2 participants