ADO.NET Data Service API Versioning -


We created the main entry point of our central application at the top of our ADMX file. In the near future, many different applications will show and consume our REST service.

So far, it's great, but one thing I am missing is that I have been using ADOs for all my consumers every time. Net does not want to update to publish a new version of Data Services. How can I get such a legacy compliance?

Thank you, Stephen.

Data services clients and server connections do not make version annotations on time - they do it for each request. Each request or response contains a version header that indicates which version of the customer or server it is required to request. This means that the downlaw client can communicate with an up-level server, as long as the server can not respond to those requests, which requires the version number of the response to it. To use the highest version responses, the service is required, all of which are off by default.

This means that as a new version of the data services is published, the customer and server will continue to be able to communicate with each other, which is not installed on the client version, despite this the new features The server is not enabled on the server, for which it is necessary to respond to the highest version client.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -