Already a member? Log in

Sign up with your...

or

Sign Up with your email address

Add Tags

Duplicate Tags

Rename Tags

Share It With Others!

Save Link

Sign in

Sign Up with your email address

Sign up

By clicking the button, you agree to the Terms & Conditions.

Forgot Password?

Please enter your username below and press the send button.
A password reset link will be sent to you.

If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.

ADVERTISEMENT

Links 1 through 10 of 95 by Alan Dean tagged Roy.Fielding+[rest-discuss]

Roy Fielding: "Doing RESTful actions on multiple resources is no different from
selecting multiple tunes in iTunes and using the info dialog
to set certain properties across all selected tunes. It is a UI issue.
The UI builds a set of actions to perform and then performs them
in whatever way is most efficiently provided by the set of resources
being operated upon. If those resources (or, rather, the index to
those resources) say they can be operated upon as a group by POST
of a selection form, then so be it -- that is perfectly RESTful
even without the benefit of per-resource cache invalidation.
Likewise for PATCH or PUT to a meta-resource, or PROPPATCH to a
WebDAV resource, it is RESTful if there is some engine described
by a representation provided by the origin server that instructs
the client on what to do next.

The goals are to remove coupling and maximize the number of
reusable resources."

Share It With Others!

Roy Fielding: "[…] the purpose of REST is to force the developer into a less object-specific architecture, which is contrary to most of the OOD patterns. Whether that is good or bad depends on what is being implemented."

Share It With Others!

Roy Fielding: "An HTTP server's URI-space has nothing whatsoever to do with its storage space, aside from that created by the handlers within that space."

Share It With Others!

No, the point of REST is to model a Web service. It wouldn't be complete if it neglected to include query parameters. However, it works best when query parameters are only used read-only and result in a list of metadata and specific resource identifiers.

Share It With Others!

REST does not require that a URI be opaque. The only place where the word opaque occurs in my dissertation is where I complain about the opaqueness of cookies. In fact, RESTful applications are encouraged to use human-meaningful, hierarchical identifiers

Share It With Others!

Roy Fielding: "All links are wishful thinking. Guessed links are just somewhat more wishful than others."

Share It With Others!

Seairth Jacobs: "Is OPTIONS supposed to be non-cachable for everyone or just intermediaries?" Roy Fielding: "It is only non-cacheable by default. Use cache-control to change that."

Share It With Others!

Roy Fielding: "Good grief. Why does everyone equate REST with HTTP? REST apps work quite well with file, ftp, gopher, wais, urn, ... I won't even mention waka in that list because it isn't done yet."

Share It With Others!

Roy: "And to think I went to all that trouble coming up with an acronym that would be an easy pun. 'No REST for the wicked.' 'I just spent all day reading about Web Services. I need some REST.' 'I got up too early this morning. (not enough REST)'"

Share It With Others!

Roy: "At least one form of OPTIONS request was always intended to contain the desired (later) request in the OPTIONS body (excluding the body of the desired request itself), thus allowing the server to know exactly what options should be described."

Share It With Others!

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT