On 5/4/06, Tim Bray <[EMAIL PROTECTED]> wrote:
On May 3, 2006, at 3:55 PM, Thomas Broyer wrote:
> I also still don't understand why the response body, if provided,
> "must" be an Atom Entry Document:
Bah, we discussed this a *lot* and I thought it was pretty clear the
WG had consensus for an Atom entry or nothing. -Tim
If an entry is provided, I can get atom:[EMAIL PROTECTED] (to UPDATE or
DELETE immediately after POST "oops this wasn't supporsed to be public."),
atom:[EMAIL PROTECTED] (to browse HTML page or some image "yap
looks good with the css"),
atom:[EMAIL PROTECTED] (to replate media file "oops wrong file"),
atom:[EMAIL PROTECTED] and atom:id.
I'm probably going to use atom:id as a primary key to save local copy
of the entry.
I used to use edit uri(atom:[EMAIL PROTECTED]) as primary key, but as GDATA
suggests it changes!
So, I'm hoping that all server would return the Atom Entry Document...
Now, what if the server generates a response with a status
code other than 201 such as 400 ("Bad Request") or even
500 ("Internal Server Error")?
It would be helpfull if server returns some explanation of
the rejection or error.
Some server implementation out there which I'm kicking
around lately returns error body like below.
HTTP/1.x 500 Internal Server Error
Content-Type: application/xml
<error>couldn't connect to the DB server.</error>
Could we standardized this?
