rest-discuss at Yahoo! Groups

Re: Appropriate status code when creating a lock fails?

Subbu Allamaraju — Sat, 04 Jul 2009 23:23:03 GMT

Leaving aside the question of whether pessimistic locking over the web is a good or bad, I would expect a lock at the end of this operation. This of course,

Re: Appropriate status code when creating a lock fails?

Jan Algermissen — Sat, 04 Jul 2009 23:10:05 GMT

... Because it is (currently) a requirement of the owners of the system to use a pessimistic locking strategy, IOW, not HTTPs conditional write approach with

Re: Appropriate status code when creating a lock fails?

Subbu Allamaraju — Sat, 04 Jul 2009 23:04:27 GMT

Just curious - why would the server want to offer such a functionality as locking to its clients? Subbu

Re: Resources with read-only and read-write parts

Subbu Allamaraju — Sat, 04 Jul 2009 23:04:02 GMT

Representations in a request (e.g. PUT or POST) and representations in a response (e.g. GET or a PUT) need not be absolutely the same. HTTP servers are not

Re: Appropriate status code when creating a lock fails?

Subbu Allamaraju — Sat, 04 Jul 2009 22:57:20 GMT

Just curious - why would the server want to lock a resource? Subbu

Re: Resources with read-only and read-write parts

Sandeep Shetty — Sat, 04 Jul 2009 22:03:05 GMT

Hey Jim, ... IMO, you seem to be confusing between the state of the resource and its representation. GET and PUT allow you to retrieve and set the state of the

Re: Appropriate status code when creating a lock fails?

mike amundsen — Sat, 04 Jul 2009 03:29:41 GMT

if a concurrency header is required, but missing I usually return 412 with additonal text reminding of the requirement. ... -- mca http://amundsen.com/blog/

Re: Appropriate status code when creating a lock fails?

Jan Algermissen — Sat, 04 Jul 2009 02:20:25 GMT

Doh - got things mixed up 304 should obviously have been 412 .

Appropriate status code when creating a lock fails?

Jan Algermissen — Sat, 04 Jul 2009 02:02:51 GMT

Hi, suppose a situation where clients know that creating a lock on some resource http://www.example.com/docs/1234 is done by PUTing to

Re: Resources with read-only and read-write parts

Jan Algermissen — Fri, 03 Jul 2009 03:24:08 GMT

Hi Jim, can you provide an example representation for the mutable/immutable use case? Jan

Re: Resources with read-only and read-write parts

mike amundsen — Thu, 02 Jul 2009 17:56:43 GMT

Jim: I am addressing the security portion of your post. Hopefully this will give you some ideas. there are some elements that are modifiable or not

Re: Resources with read-only and read-write parts

Sam Johnston — Thu, 02 Jul 2009 15:01:59 GMT

Jim, Typically you would express the overall writeability of a resource via OPTIONS (e.g. if you can only GET it's read only), but if you've got, say, a

Resources with read-only and read-write parts

Jim Edwards-Hewitt — Thu, 02 Jul 2009 14:43:21 GMT

Hi, everyone, I'm a newbie here (though not to REST in general), and the list archives have been a great help in clarifying my understanding of a lot of REST

Re: Using HTTP Link: headers for web linking non-hypertext

Sam Johnston — Wed, 01 Jul 2009 23:18:30 GMT

... Ok so here's a separate but similar issue. I've just released an Internet-Draft

Re: Using HTTP Link: headers for web linking non-hypertext

Subbu Allamaraju — Wed, 01 Jul 2009 16:37:46 GMT

... They (browsers) do not. But that is besides the point for this thread. The key question being debated is whether link management is a client concern or it