2006/5/9, James M Snell <[EMAIL PROTECTED]>:
There are valid reasons why one may want to separate the edit and edit-resource URI's (e.g. the media resource is stored on a different host than the entry).
Do you have examples? I can understand the CDN use case, where the atom:[EMAIL PROTECTED]"edit-resource"] is different from the atom:content/@src (there might be caching problems here, but that's another story), but I can't understand the need for distinct "edit URI". I mean, there have been consensus last fall that a collection "list membership" and "add member" endpoints have to be the same, and that the server can act as a proxy if there's a need for them to be distinct (dispatching depending on the request method; that was the invoked reason for rejecting PaceDecoupleCreateAndListEndpoints), why couldn't we have a similar constraint here (dispatching depending on media type; note that it's not conneg, it's far easier than conneg! and not any harder than request-method dispatching). -- Thomas Broyer
