OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [camp] Issue 3: alternate proposed direction

+1 to not managing PDPs. If we did we would need to define a resource to represent them, specify their lifecycle and the operations necessary to manage that lifecycle (e.g. "update PDP"), etc. I don't see any advantage in CAMP getting into content management.

~ gp

On 5/18/2013 5:31 AM, Alex Heneveld wrote:


We don't currently track PDP's at the platform. How about the POST returns an assembly template?


On May 18, 2013 12:28 PM, "Anish Karmarkar" <Anish.Karmarkar@oracle.com> wrote:
Here is an alternate proposal for uploading a PDP that does not involve MIME, as promised:

1. Uploading a PDP to the Platform

To upload a PDP, a client send a HTTP POST request to the Platform URL with the PDP in the entity body of the request (Note: media-type of the request is TBD). On success, the server returns a 201 Created HTTP status code with the Location header that contains the URI that identifies the uploaded PDP.


POST /<platform-url> HTTP/1.1
Host: example.org
Content-Type: ...
Content-Length: ...

... <PDP> ...

HTTP/1.1 201 Created
Location: http://example.org/paas/pdps/1
Content-Type: ...
Content-Length: ...


Note that the client can use the value of the 'Location' header in the HTTP response to register the PDP as described in Section 6.11. The same uploaded PDP may be registered by the client more than once.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]