Hello; Most of the discussion around REST that I can find refers to HTTP as the only transport used. While I understand that REST is an Architectural Style,...
... [hvw] I'm not quibbling when I remark that HTTP is an application protocol, not a "transport". It's a protocol for apps that transfer hypertext messages ...
Hugh, ... There could be a lot of them, as long as they make sense when applied to *any* resource: example: GET /my/bank/account (good) example: LOCK...
... HTTP is not a transport protocol. Abusing HTTP to serve as a transport protocol is one of the things that can lead to people not taking advantage of the...
... [hvw] Excellent point. Further thoughts: One reason the web has been successful is that REST enabled all kinds of apps to run using this simple protocol....
You might say that message-oriented middleware (MOM) follows the REST architectural style. * resource identifier = topic/queue name + message ID vs. URI *...
... And hypermedia. And caching/cache-control. And pull vs. push. ...jsled -- http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo ${a}@${b}`...
And all notions of state management.... When I see "GET [uri]". I know what the response represents, and I know that the operation did not change the state of...
... Message buses can support hypermedia representations, just as HTTP can support non-hypermedia. Most messaging systems do support caching: clients can...
... So would I if that was what I wrote, but it isn't. Dissertations are a successful walk through a minefield -- summarizing them is not. One of the...
Hi people, I'm new in REST universe and I want to validate a user with a password using REST philosofy, but the unique method that I thought ... POST /auth...
One of the problems that I keep on bumping up against is "what's a good data model for a URI?" In particular, how do you represent the path? (For the purposes...
... I usually leave it as a single string, which makes it really easy to do pattern matching: <path>/foo/</path> I just wrote some code using your #1 (parsing...
... I treat paths as tuples delimited by '/', so /foo/bar and /foo/bar/ are both the {foo,bar} tuple. This abstraction hasn't caused any problems in terms of...
... Treating it as a tuple (foo,bar) works for me as well. BTW, when I see {foo,bar} my mind parses that as a set :)...
Sandeep Shetty
sandeep.shetty@...
Oct 9, 2005 10:35 am
5276
... My mistake. Re-reading with emphasis on "unregulated" I now see exactly what you were saying. Looking at Rohit's <http://www.ics.uci.edu/~rohit/>...
... I'm really down on defaults these days. So if you're not going on vacation, it would be #3 ;) I liked Lucas' syntax btw; maybe y'all should use json or...
... This only indirectly answers your question, but - for messaging (HTTPLR) I came to the conclusion that URLs be issued by the server via a Location header....
... There are large number of unused resources, what is your definition of 'next', and what is the significance of sequence for these resources? With PUT, the...
... 'next' : next in the sequence. Often data modellers choose sequences without good reason. For example 1: Slashdot users get the number numerically, ...
... The 2) would have to be a POST, as the PUT request contains the URI of the resource. A PUT request means "make the resource 'uri123xyz' look like this ...
... I'll skip the analogy to C++ pointers and memory addresses, and suggest that a document with explicit 'next' and 'prev' URI references work for a queue and...
... Maybe we can look on the intention of a request. If a client request to server, "please use this XML data to create a new entry". Here, "create a new...
... I have beat this hobbyhorse before, so have to apologize to the many people who have already seen it, but my "Secure Protocol for Desktop Web Servers"...
Lucas, Interesting paper, and one I had not seen before (as a relative newcomer to rest-discuss). One possible addition to your work: since many clients sit...