PreCacheMaps effectively does a MgMap.Create() on each Map Definition specified, thus pre-caching any associated Feature Sources, Schemas, Class Definitions and Spatial Contexts needed by the MgMap.Create() call.
See: http://themapguyde.blogspot.com.au/2012/10/mapguide-server-cache-priming.html All cached objects are timestamped (at the time they are retrieved), and CacheTimeLimit is what a regularly-scheduled function in MapGuide uses to check for which cached items need to be removed. The logic being: Remove any cached object that has not been accessed for <CacheTimeLimit> or more seconds. So I think that bumping up that number should indeed do the trick. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Map-frame-display-delay-tp5072746p5073064.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
