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

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

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


Subject: [OASIS Issue Tracker] Commented: (ODATA-159) Handling inline attachments in requests/responses


    [ http://tools.oasis-open.org/issues/browse/ODATA-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32654#action_32654 ] 

Ralf Handl commented on ODATA-159:
----------------------------------

I second :-)

> 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 
>         Environment: [Proposed]
>            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?
> Original proposal:
> 1. Media Entities can contain content INLINE
> 2. Or OData can support multipart message format with the first part having the original request/response payload in atom/json formats and rest of the parts having attachments as dealt in case of HTTP multipart attachments.

-- 
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

        


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