The delay is generally the first MgInitializeWebTier() call in the IIS application pool and the first time a MgMap is created.
Subsequent MgInitializeWebTier() calls return immediately and subsequent MgMap creations off the same Map Definition would be working with cached information. I don't know if such delay can be avoided the first time round. Something *has* to wear the time cost to initialize the web tier before any application can start using the MapGuide API and something *has* to wear the time cost to prime the caches, for fast subsequent MgMap.Create() calls. Now if it's happening for the 2nd, 3rd, 4th, etc time round then I'm guessing the cached information has expired had has been flushed out by the MapGuide Server. There's probably a serverconfig.ini setting somewhere that controls the lifetime of cached objects. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Map-frame-display-delay-tp5072746p5072771.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
