On 4/25/06, James M Snell <[EMAIL PROTECTED]> wrote: > > Mark, > > The key challenge with this is that the server is given free reign over > the posted entries metadata content. It can change anything and > everything about the entry once it has been posted, including it's > atom:id. If an Atom entry is not returned in response to the POST, the > client would have to first perform a GET on the Location URI to get the > atom:id before they could match what they POST'ed to what shows up in > the Collections Atom feed, which works, but is inefficient. Making the > response mandatory eliminates this problem.
Sure, but at the cost of removing the possibility of future extensibility, profiling HTTP, and requiring bandwidth be wasted in many cases. But MUST for an optimization? If you specified nothing here, then servers would have the option of returning the entry if that something they felt their clients needed, or a particular interaction required, or had otherwise negotiated with an authenticated client. But they'd also have the option of returning anything else, or nothing at all, should some yet-to-be-defined feature want to do so in the future. And as you say, they can always GET if they need to. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
