If you ran CREATERUNTIMEMAP many times on the same map definition and same set of parameters, the only difference in the responses you get back are the session ids. Thus the caching opportunity is to save the rest of the XML response as a cached "template" and for subsequent requests of the same map and parameters, just fetch the stored template, plug in the new session id, make the new MgMap/MgSelection in that session's repository and return that plugged in XML response.
Still, I don't think this is the actual problem at hand. It might be a bit slow on some big map definitions, but not "30 seconds" slow. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/30-seconds-delay-after-creating-100-CreateRuntimeMap-calls-tp5309691p5310028.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
