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: RE: updating OData client


Hi Ed;

 

As you say, OData V4 does define enhancements to the V3 specification and does not represent a fundamentally new model. Note, though, that while a service that implements OData V4 can also support V3, there are breaking changes between OData V3 and V4, such as the simplification of relationships in the data model, which means that a V3 client will not be able to read a V4 response, and a V4 client will not be able to read a V3 response without understanding the differences in the V3 syntax.

 

If you already support the "JSON Lite" format in OData V3, supporting the OASIS OData V4 JSON format is pretty straightforward, but there are significant differences between the OData V1-V3 "Verbose" JSON format and the new OASIS OData V4 JSON format.

 

OData also defines new functionality, like deltas and asynchronous processing. While clients are not required to implement such functionality, they represent incremental work for cases where the client wants to take advantage of such functionality.

 

All that said, 50% of the initial investment seems a reasonable ballpark for supporting the same level of functionality in a V4 compliant manner. Hopefully it would be somewhat less than that, giving you some buffer to implement some new things like deltas, but it seems to me like a reasonable ballpark.

 

I hope this helps,

 

-Mike

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Ed Bourne
Sent: Wednesday, November 20, 2013 6:58 AM
To: odata@lists.oasis-open.org
Subject: [odata] updating OData client

 

I’ve been asked to ball bark the effort for updating the C++ client to V4 of the spec.  

 

My guesstimate is that it should take about 50% of the effort that created it in the first place because of 2 assumptions:

1)      That OData is backwards compatible, server responses to the client are sensitive to the clients ability.

2)      Most of the changes in the V4 spec are enhancements on the existing spec, not requiring any new fundamental change (ie like the addition of JSON support in the past).

 

That seem reasonable to the group?  Anything I’m missing?

 

 

cheers

 

Ed Bourne | 519-597-2863 or Toll Free: 1.888.746.5831 x72863 "Reach Me Anywhere"

Sr. Enterprise Developer, Enterprise Developer Partnerships

 cid:image001.gif@01CE047A.9B1970A0cid:image002.jpg@01CE0AA4.D6F6DCE0

 

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.



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