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] Updated: (ODATA-297) State explicitly if Content-Length is required, and if so, for which request types it is required


     [ http://tools.oasis-open.org/issues/browse/ODATA-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-297:
--------------------------------

       Proposal: Do not add any requirements over HTTP for writing content-length
    Environment: [Proposed]

OData should not add any requirements over what HTTP already specifies.

According to HTTP, Content-Length "SHOULD be sent whenever the message's length can be determined prior to being transferred, unless this is prohibited by the rules in section 4.4." 


> State explicitly if Content-Length is required, and if so, for which request types it is required
> -------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-297
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-297
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Evan Ireland
>
> The procotol spec (2013-03-12) shows some examples in section 9.6.210.6.2 Batch Request Body, which include Content-Length.
> But no examples or requirements are provided for the use of Content-Length elsewhere.
> We should state explicitly when Content-Length must be specified (if at all).
> Note: Content-Length is particularly valuable for clients accessing large Stream values, as it allows the client applications to provide progress meters in the UI.
> It is less useful for clients accessing entity sets, as the server may (via the use of nextLink) break up a response into multiple pages. If clients could indicate via a preference that they wish to receive an entire entity set (or delta link contents) in a single HTTP response, then Content-Length would be quite useful for entity sets and delta links.

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