[ http://tools.oasis-open.org/issues/browse/ODATA-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31599#action_31599 ]
Anila Kumar GVN commented on ODATA-159:
---------------------------------------
Thanks for your quick response Ralf.
The problem with going with existing batch processing semantics is that as per the spec, 'Nth' part of a multipart request corresponds to the payload of 'Nth' operation in the batch request which is not true in this case. Nth operation may have payloads based on Nth, N+1th or more.. based on no. of attachments to that operation.
It looks like a misuse of existing batch processing semantics and what we are looking for is a standard way which doesn't break the spec and still respond to a request with attachments as part of the response itself rather than just media links.
Does this align with design principles of OData?
> Handling inline attachments in requests/responses
> -------------------------------------------------
>
> Key: ODATA-159
> URL: http://tools.oasis-open.org/issues/browse/ODATA-159
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: New Feature
> Components: OData Protocol v1.0
> Reporter: Anila Kumar GVN
>
> The only way of dealing with attachments (streams) as per the current OData spec seems to be using Media Entities or Named Stream Properties, where a media link is provided to download the attachment. Is there a way to get properties and attachments in one call?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
