This can be useful when accessing xServer behind a firewall, allow cross-domain and cross-scheme calls, add some load-balancing or fail-over, tile-caching, etc. You can also use your own authorization or inject xServer credentials inside the middleware. For example, you can add your xserver internet token and don't have to expose it in JavaScript. The web-client can still use xServer in exactly same way as it does for a direct access. See here for more infos: http://xserver.ptvgroup.com/en-uk/cookbook/best-practices/xserver-internet-with-different-frontend-architectures/
The JavaScript sample-code is based on https://github.com/ptv-logistics/PoiLocator, but all calls go through the XServerProxy.ashx rather than calling xServer internet directly.
For more samples with xServer in combination with ASP.NET, you should also take a look at https://github.com/ptv-logistics/WebFormsMap or https://github.com/ptv-logistics/SpatialTutorial.
To use this code with xServer internet, you need an xServer internet subscription. Go to http://xserver.ptvgroup.com/en-uk/products/ptv-xserver-internet/test/ to get a trial token.
This is a javascript/ASP.NET sample that loads some data from an ASP page and does some geographic visualizations and operations on it. For map-display and geographic operations PTV xServer is used. Unlike the other xServer/JavaScript samples, the xServer isn't accessed directly from the client, but through the middleware that hosts the web page.
- Add the the XServerProxy handler code to your ASP.NET project
- Add a rewrite rule in your Web.config (requires ARR & IIS rewrite module)
- Adapt the code for your xServer infrasctructure. I've added sample for xServer on-premise and xServer internet
- Make your xServer internet requests with the relative url, like /XServerProxy/WMS/WMS or /XServerProxy/xlocate/rs/XLocate/findAddressByText.