Re: app:accept and Atom entry MIME type

[Al Brown <albertcbrown@xxxxxxxxxx>]

Thanks Julian. I knew I should have checked with you first. That leaves 415, 422, and 500 to handle the feedback to the client.

-Al

Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home

Office 714 327 3453
Mobile 714 263 6441
Email albertcbrown@xxxxxxxxxx
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.

Julian Reschke ---05/19/2009 09:39:43 AM---Al Brown wrote:

From:	Julian Reschke <julian.reschke@xxxxxx>
To:	Al Brown/Costa Mesa/IBM@IBMUS
Cc:	"Roy T. Fielding" <fielding@xxxxxxxx>, atom-protocol Protocol <atom-protocol@xxxxxxx>, Nikunj Mehta <nikunj.mehta@xxxxxxxxxx>, owner-atom-protocol@xxxxxxxxxxxx, pjkeane@xxxxxxxxx, Peter Keane <pkeane@xxxxxxxxxxxxxxx>, Ryan McVeigh <ryan.mcveigh@xxxxxxxxxx>
Date:	05/19/2009 09:39 AM
Subject:	Re: app:accept and Atom entry MIME type

---

Al Brown wrote:
>  >Why would the request fail?
> If the server has no intent to support non-cmis documents, then it would 
> not advertise it supports those media types.  Adding profile="" or 
> cmisprofile=1.0 to the atom media type solves the signaling issue. If 
> the repository does advertise it supports those media types, then it is 
> a configuration issue of the underlying repository due to a) no default 
> type available b) default type requires information not specified or c) 
> some other resource not available (network between tiers, database, 
> storage, etc)
> 
> 
>  >AFAICT, there is
>  >no need to do so.  Just send the AtomPub/HTTP message to the server.
> 
> The server could return the following to handle the scenarios:
> 
> 412 Precondition failed (httpbis[1]) (a or b)

That's for conditional requests (like "if-match: ...").

> 415 Unsupported media type (httpbis) (if the request is in a format 
> other than what is allowed; e.g., missing cmis extensions)

Right, or potentially 422 Unprocessable Entity 
(<http://greenbytes.de/tech/webdav/rfc4918.html#rfc.section.11.2>)

> ...


BR, Julian