Not just the AT, but all the other resources in the PDP AT hierarchy
as well.
This doesn't allow you to update an existing AT hierarchy however,
each time a new one is created...
-- mark
On 5/18/13 9:41 AM, Adrian Otto wrote:
Yes, if you POST to a platform, you should expect an AT to be
created. Otherwise, how would you create them? If you POST to
the AT, you get an Assembly.
--
Adrian
On May 18, 2013, at 5:32 AM, "Alex Heneveld" <>
wrote:
Anish,
We don't currently track PDP's at the platform. How about
the POST returns an assembly template?
Best,
Alex
On May 18, 2013 12:28 PM, "Anish
Karmarkar" <>
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.
Example:
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.
Comments?
-Anish
--
