[mapguide-internals] Avoiding unnecessary Tile Cache invalidation (Trac Ticket 1332)

[Tom Fukushima]

Yes, good points.

BTW, in a previous response, you said that "Pushing tile sets into a separate resource would ensure that only changes affecting the tile set would trigger a flush of the cache", but it's not quite that simple.  For example, if the user changes the legend label of a layer or theme, or the tooltip of a layer, these will signal a change to the resource but there is no reason to flush the cache. 
 
Tom

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, April 28, 2010 9:13 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Avoiding unnecessary Tile Cache invalidation (Trac Ticket 1332)

Gmail won't let me change the follow-up subject...  :(

Anyway, I originally though the references should stay in the MapDef too,
but there are some benefits to moving it into the AppDef / WebLayout.  The
Fusion AppDev already conceptually (though possibly not functionally)
supports multiple MapGuide MapDefinitions in addition to Google, etc base
layers.

My guess would be that adding support for referencing a MapGuide tile
resource directly rather than as a MapDefinition may be easier than
modifying the MapGuide layer type to point to external MapGuide base layers,
and would be more in keeping with the general OL "layers" concept.

Not sure how this would apply to AJAX viewer though; it's likely a lot more
work on that side.

Jason