Some guidelines are already common within the larger REST communities:
- Applications should expose many URIs (possibly an infinite number of them), one for each Resource (any resources in your applications should be unambiguously accessible via a unique URI)
- Cookies representing IDs into a server side session are not RESTful
- Combinations of resources (i.e. a particular account viewing results a particular database query) can be RESTful if (and only if) the combination can be represented as a URI.
- RESTful URIs should facilitate "cut & paste" (that's the notion of "transfer" of the "representational state")
Read more about this topic: Resource-oriented Architecture
Other articles related to "common guidelines, guidelines":
... Guidelines for choosing good passwords are designed to make passwords less easily discovered by intelligent guessing ... Common guidelines include A minimum password length of 12 to 14 characters if permitted Generating passwords randomly where feasible Avoiding ... that the public or workmates know you strongly like or dislike Some guidelines advise against writing passwords down, while others, noting the large ...
Famous quotes containing the word common:
“There is a certain wisdom of humanity which is common to the greatest men with the lowest, and which our ordinary education often labors to silence and obstruct.”
—Ralph Waldo Emerson (18031882)