... I've been playing with both JMS and REST recently and at first, I was trying to see how REST could be used instead of JMS. I came to think that these 2...
... Yes, it's the representation that's cacheable. My point is that when a resource has only one representation, cacheability is high. When a resource has many...
... But then, the resource has to be distributed. And now the state of the resource will change as often as the session would have, had you been using one....
... No. I'm not. I was finding this difficult to explain though /8-> Here's an attempt to explain. Consider resource representations in files and a high...
Hi Mike, Thanks for the response. I wrote you back a missive myself ;) I hope someone other then the two of us finds this conversation useful. I'd love to see...
... I did something like that about five years ago : http://sourceforge.net/projects/destiny That project is more of a (working) demo but the ideas are valid &...
... Entire discussion is about whether representation meta data be addressed via Accept headers than through query string. If I am wrong just leave it at this...
When i use logical URI, I use htaccess file of apache for exmple - RewriteEngine On #RewriteCond %{REQUEST_FILENAME} !-d #RewriteCond %{REQUEST_FILENAME} !-f ...
... I can think of no reason. Just so I understand, since WebDAV is a HTTP extension, you can (re)use these codes outside a WebDav context, right? cheers Bill...
... Could someone help me understand the relationship between standard error codes and extensions please? If I got 422, how would I know how to interpret it? ...
Ideally there'd be an HTTP response code registry. Since there isn't one (AFAIK), just Google for it. http://www.google.com/search?q=http+422+response Mark....
http://www.ietf.org/rfc/rfc4028.txt seems the best, but a little unmatched to the definition earlier in this thread? Thanks Mark. ... -- Dave Pawson XSLT...
... Either: a. You'd know what a 422 meant from the WebDav spec or elsewhere, and treat it according to that. b. You treat it as an unknown error in the range...
And if so, how? I have read Roy's paper and a few other things but this cookie thing is something I just don't get. I was just having a conversation with my ...
... Yes. It's called HTTP authentication. Anything involving personal, private data should require a username password combo to access. Presumably if someone...
Elliotte Harold
elharo@...
May 4, 2006 6:13 pm
6194
... Oh. Also TLS client certificate authentication addresses the problem best. Just issue a client certificate to your customers. Then they really know who...
... I've said this quite a lot recently. I don't believe there's anything wrong with cookies. What is wrong is using a cookie to manage a session with data...
... Unfortunately nobody likes HTTP auth because the only way to authenticate with it seems to be using that ugly browser-supplied popup box which you cannot...
... This is not true. Have you not heard of AJAX? btw these issues have been discussed here a lot only just recently. You might want to go back through the...
... And I've replied to this quite recently too. It's not just about sessions. It's about boomarkability, linkability, e-mail-ability and more. A cookie is not...
Elliotte Harold
elharo@...
May 4, 2006 7:43 pm
6200
... Yes, they prefer a shiny new car that gets 10 miles a gallon and breaks down every couple of days to a old clunker that runs great and causes little pain....
Elliotte Harold
elharo@...
May 4, 2006 7:46 pm
6201
... Berend de Boer has been doing some work in this area using HTML forms and XHR, see http://www.pobox.com/~berend/rest/authentication.html Cheers Adam...
Hi Tracy, ... Session IDs in cookies can be hijacked via cross-site scripting attacks, or just sniffed on the network if they are transmitted in plain text....
Hi Rusty, ... I suspect you're primarily concerned about using a session ID cookie to lookup session state on the server, not using cookies for authentication....
... That is not true. Here's an example of a resource that would not violate REST: <html> <body> <h1>Hello <script> var arr = document.cookie.split(";"); for...