[OASIS Issue Tracker] Created: (ODATA-458) odata.isolation should be a header rather than an expectation

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

odata.isolation should be a header rather than an expectation
-------------------------------------------------------------

                 Key: ODATA-458
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-458
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol 
    Affects Versions: V4.0_CSD01
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.0_CSD02


ODATA-317 added support for snapshot isolation by specifying a new odata.isolation expect header. However, upon further research, expect headers must be understood by intermediaries or rejected. so even though a service might support snapshot isolation, intermediaries would likely return expectation failed.

We discussed making this a preference, but earlier we had said that the desired behavior was for the service to fail the request if the client specified snapshot and the service was unable to provide that level of isolation, and preferences should not cause errors.

So it seems the best way to support this functionality is to introduce a new odata header for isolation.

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