I'm not going to lie down in the road over it, but I'd much prefer the single POST approach. Either way, with it being a SHOULD and not a MUST, my client code has to be ready to do the follow-up GET anyway. At the very least, let's make sure that the optimization and the ramifications for not using it are well documented.
- James Joe Gregorio wrote: >[snip] > Both approaches work and if other people don't see the first > case as awkward I'd be OK with an Atom Entry response body > being a MAY (with a note explaining the Location: == Content-Location: > optimization). > > -joe >
