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] Created: (ODATA-168) Correlate batch request and response parts via the Content-Id header


Correlate batch request and response parts via the Content-Id header
--------------------------------------------------------------------

                 Key: ODATA-168
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-168
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData Protocol v1.0
    Affects Versions: WD01
         Environment: [Proposed]
            Reporter: Ralf Handl
             Fix For: WD01


Currently the response to a batch request must contain the response parts in exactly the same order as the corresponding request parts.

A more explicit correlation could be achieved by copying the Content-Id header from the request parts to the response parts, so clients providing this header could correlate the parts based on this header value.

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