Page 1 of 1

FYI: Named xServer 2.x versions on xServer Internet

Posted: Wed May 16, 2018 4:03 pm
by Bernd Welter
Hi there,

as some of you might know we have implemented a feature in the xServer2 framework that enables us to offer various service URLs based on the following "perspective" (example: xLocate).
Unfortunately some of the developers were missing this named versions and we do not want to have such an effect on production. Therefore we want to let you know:
  • We recommend to use the named versions on production of xServer INTERNET. This will ensure a stable request/response structure without any new response properties which may "surprise" your client code ;-)
  • We will keep the named 2.6 version with the production update to 2.7 (already processed) but we will remove the named version with version 2.8. UPDATE 11.2.2019: The activation of named versions has no significant impact on performance and we therefore decided to enable them all on the xServer internet 2 cloud ;-)
Named Versions:<br />- HEAD<br />- EXPERIMENTAL<br />- explicit version<br />Screenshot taken from production https://xserver2-europe-eu.cloud.ptvgroup.com/dashboard/Default.htm#Administration/Services.htm
Named Versions:
- HEAD
- EXPERIMENTAL
- explicit version
Screenshot taken from production https://xserver2-europe-eu.cloud.ptvgroup.com/dashboard/Default.htm#Administration/Services.htm
  • HEAD : this refers to the latest status of the released product features. A feature that was released will stay part of the future deployments
  • EXPERIMENTAL : regular features plus some upcoming features marked as experimental. Experimental features are subject to change. We might therefor remove properties, parameters or even complete methods from the service - depends on our experience and your feedback
  • VERSION : there's also a version tagged URL which refers to a subset of those features that were part of this specific version.
The difference between current and head:
- Current: is the current VERSIONED API – the path to that changes every Version. But you are able to integrate a fixed and stable API, also for following versions, when you configure and address this particular API Version.
- Head: This path will always point to the latest API – and this may contain some extensions from one Version to the next. And maybe cause some Problems, if result objects are not handled correctly by the client.

Best regards,
Bernd

PS: do not hesitate to get back to us if you have question - we want to ensure that your production is not affected ;-)


Update 29.8.2022 - little example for C#:

Code: Select all

RouteRequest routeRequest = new RouteRequest
{ ... };

XRouteClient svcRoute 
= new XRouteClient("https://xserver2-europe-eu-test.cloud.ptvgroup.com", "2.21");
         
BasicHttpBinding binding = new BasicHttpBinding { MaxReceivedMessageSize = 2147483647 };
binding.Security.Mode = BasicHttpSecurityMode.Transport;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Basic;
svcRoute.Endpoint.Binding = binding;

svcRoute.ClientCredentials.UserName.UserName = "xtok";
svcRoute.ClientCredentials.UserName.Password = Properties.Settings.Default.TOKEN;

RouteResponse routeResponse = svcRoute.calculateRoute(routeRequest);