On 24/1/06 6:45 AM, "James Holderness" <[EMAIL PROTECTED]> wrote:
> I'm not going to be thinking, you know what, just to be safe I'll go and > enumerate the media collection and see what URI it has for this entry. And > even if I did decide to do that, there is no way for me to know which entry > in the media collection matches up with the media resource I just posted. > That's a gaping hole in the spec. That's bugged me too. If posting a binary to a media collection results in an Atom Entry being created which references the binary, why can't the Location header point to the Atom Entry in the first place ... at least the client can then use that to find everything else they need. e.
