On 5/9/06, Kyle Marvin <[EMAIL PROTECTED]> wrote: > It's less of an issue (at least to me) if the entry and media are > non-intersecting representations, but even there a purist might argue > that they are two separate resources (but not two separate *entries*) > and overlaying them behind one resource uri is wrong.
I'll be even more specific on the intersecting vs. non-intersecting cases: I can live w/ the non-intersecting case because it is transparent to the client; they don't have to know our think about the fact that a PUT to the 'media' resource will result in a side-effecting change to the 'entry' resource. The client code should always be written to view the 'edit' and 'edit-resource' as two separate pieces of data that are independent of each other (beyond link references). Anything that blurs this distinction in a client-visible way seems dangerous to me... suddenly some defensive coding (to make sure you have an up-to-date representation of the two resources while editting) becomes required. -- Kyle
