... Mark, You bet -- I believe many detailed examples will help to demystify _how_ REST actually works in practice and this will let people appreciate it even...
Interesting reading. No mention of REST, though. REST would address some of the issues. Some of you will be seeing this for the thrid time ;-), but it has been...
Since I'm unable to post to the rest-discuss list (or even find out why I can't post), I'll post this here and hope that some of the interested parties read...
... I'm very confused by this. Once a socket is established, it's a bidirectional, full duplex pipe. There is no "direction" in any meaningful sense....
... I understand, but there's a bigger issue; "direction" is not a transport layer concern, it's an application layer concern. So anything you want to do with...
... Yeah, me too Mark. Paul, sorry, but this is serious braindamage. (That's okay, we all go through it periodically.) But this makes no sense at all. From...
Jeff Bone
jbone@...
Jul 12, 2002 4:19 am
84
... But that's exactly my point. The directionality of the TCP connection creation should not force the direction of the request/response connections. Today,...
Paul Prescod
paul@...
Jul 12, 2002 5:14 am
85
On rest-discuss, Mark Baker mentioned application layer routing in conjunction with hyperlinks for change propagation to dependent resources. (Was that...
What are the issues with sending HTTP requests with a fully qualified URI in the request-uri line? For example, if two business partners are conducting...
... they both ... that ... messages ... [...] ... advisable ... Ignoring the technical protocol issues, I think it is a really bad idea from the business...
... keep ... That's also a big reason why hiding all this evidence inside proprietary internal business apps will be a loser in the medium-to- long term....
... But if it's the *same* resource, why should it matter? Or did you perhaps mean that by virtue of being "held" by both parties, that it really is two...
... not ... bad ... PUT ... I think you snipped a sentence that would have clarified my point. It is fine to have one order resource (or two, I don't care,...
... From: "Mark Baker" <distobj@...> ... The only technical issue I can see right now is: - listeners/handlers/services/etc. are limited to one-per IP...
... Okay, but PUTs can themselves kick off a process whereby the changes are verified. So it doesn't have to be a unilateral change without following the...
... I'm aware. Maybe it's just another preference item. But if you want to the change order to be a Web resource in its "offered" state (before it's accepted)...
... Hmm, I'm not sure. I used the term in relation to GET as a purely degenerate form of state alignment transaction. I understand that WS people tend to...
REST would be much more popular if it had a usable reference implementation. And it would be even better if the reference implementation itself became popular....
Sounds good, let us know when you're done. 8-) Actually, KnowNow has a system similar to this, though more basic, as one of their demo apps (at least last time...
... ? ... I'll check it out when I get time, but really want this to be very low-tech and technically undemanding. "Simplest thing that could possibly work" in...
Mark Baker wrote in http://lists.w3.org/Archives/Public/www-ws-arch/2002Aug/0282.html ... I'm not sure where you're going with this, but am concerned if you...
... Right. Workflow is top-down, it controls application state. Hypertext more "suggests" it by presenting a view of the same kind of flow that a workflow...
What do people think of this syntax/pseudo-code for describing http operations? // get content = server.resource("someURI"); // put server.resource("someURI")...
I agree with GET and PUT, but not POST. How about instead: content = server.resource("someURI") << content; Since POST can get content back, that's why I...
It also highlights the phenomenon of trying to extract all the meaning behind "Representational State Transfer" from just those three words, something more...
