So, if you modify the runtime map, the tile cache no longer pulls images from Repositories/TileCache, but starts storing tiles under the session? That's bizarre.
I know that RFC11 tried to move away from using the session repository for anything tile-based, but I wonder if the line "if a map's tile cache is cleared or its MapDefinition changed, the corresponding MgMap serialized form will be removed from the cache" has anything to do with the behaviour you are seeing. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc11 In general, the MapGuide tile cache could definitely stand some improvements, especially in making it easier to develop persistent tile caches that can be shared by multiple maps (including runtime maps) and without fear of invalidating the cache. Jason -----Original Message----- From: gingerbbm Subject: [mapguide-users] TileCache, dynamic layers, and the Session If I'm dynamically adding a session-specific layer to a map that employs base layer groups (i.e. tiles), is there any way to avoid having a session-specific tile cache generated? The dynamic layer is served via a separate request (GETDYNAMICMAPOVERLAYIMAGE) as a separate image - so in theory I should be able to have one tile cache used by all sessions. If this isn't possible it rather defeats the object of having a tile cache at all. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
