[mapguide-internals] RFC required for tile caching changes?

[Traian Stanev]

What exactly are the problems? Is it file system dependent?

Traian



-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Chris
Claydon
Sent: Friday, January 12, 2007 1:39 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RFC required for tile caching changes?

We have found that problems can occur if too many cached tile images are
stored in a single folder on the hard drive. For this reason, I have
some changes to submit that ensure that we only store 900 tiles per
folder (in 30 x 30 blocks).

This changes the locations of stored tiles, by introducing new
subfolders, and will thus "orphan" any tiles already created by the
cache. Since the root folder for the tiles for any given map will not
change, these orphaned tiles will be cleaned up if the user modifies the
map definition or makes a call to the Clear(MgMap* map) method in the
tile service API. The user could also force the cleanup simply by
deleting the contents of the root cache folder when they upgrade to the
version containing these changes.

I'd like to treat this submission as a simple defect fix, but the
requirement for the extra cleanup steps may indicate that an RFC is
required, and I'd like to know the opinions of the PSC on this matter.

Also, please let me know if you require any further information about
this submission.

Cheers,

Chris Claydon. 

_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals