MapDotNet Server 2007
Release Notes for Version 6.1.2
Release Date: 9/5/2007
Release notes contain important information available at the time of the Version 6.1.2. Please read this for information as to what changes have occurred since MapDotNet Server 2007 Version 6.1.1.
Version 6.1.2 is a maintenance release. Any applications built on version 6.1 should move over with very little effort. Please see Upgrading from 6.1 to 6.1.1 for more information.
1. Substantially improved rendering speeds with ArcSDE. This is especially the case in large multi-processor web garden deployments where the MDNS services are less likely to be processor-bound. Substantially improved SDE connection pooling resulted in upwards of 10 times the rendering performance in our tests. This was especially noticeable when ArcSDE is installed on a separate server from the MDNS web services.
2. Improved locking support for ArcSDE where large numbers of spatial queries/edits/transforms and map renderings are occurring simultaneously. The ArcSDE ESRI client API used by our query/edit/transform connectors (separate from rendering) is not thread safe and under heavy load faults were encountered. This has been resolved through better locking in MDNS.
3. Issue with web service call GetCustomLegendIcon(...) where the supplied scale was out of range of any class breaks
4. Query, Edit and Transform connection information caching support - this improves average transaction time slightly but improves latency noticeably under heavy simultaneous map rendering and query/edit/transform transaction loads.
5. Password encryption of map file connection strings was already supported in 6.1.1 for rendering but not for spatial queries/edits/transforms. The support has been extended to include these as well. Read more...
6. The Virtual Earth Extended Template has been bundled with the installers. This is the same Virtual Earth template that has come with all the 6.1 releases except with the addition of two pages (VEMap2D.aspx and VEMap3D.aspx). These pages are provided as prebuilt applications for those who wish to have a site up and running quickly with minimal effort. For custom functionality, it is still recommended to use the base page (Default.aspx) as a starting point.
Release Notes 6.1.1