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

[Jason Birch]

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

On 28 April 2010 06:19, Tom Fukushima  wrote:

> Sorry, when I wrote "This is only about the problem in the ticket", I
> should have said "This response from me is only about the problem in the
> ticket". I didn't mean to say we should ignore the "shared tile sets" idea,
> and I think it is something that is a good idea and would be good to do. I
> just don't have any input for it right now. Well, except that I think the
> reference to the tiled/base layers should stay in the MapDefinition...but
> that's just my feeling and further investigation needs to be done.
>
> Tom
>
>