[mapguide-users] Guestion about speedup mapguide, diferent domainname to mapagent.fcgi.

[Jason Birch]

This would be cool in combination with a custom error handler, which
would be used to generate missing tiles, return a 404 if the tile
genuinely doesn't exist, or a 50x error on server issues.  It would also
allow you to take advantage of all of the great caching capabilities
that you get with the web server, including the ability to respond to
if-modified-since queries by default.

I'm not sure why the restriction of one base layer group only per map?
Couldn't you set the root of the tile cache directory as the virtual
directory, and then have access to all of the groups?

I would love to see this, especially in combination with TMS :)

http://wiki.osgeo.org/index.php/Tile_Map_Service_Specification

Of course, as we've discussed, there are some incompatibilities between
TMS and MapGuide's caching scheme that would need to be resolved.

Jason 

-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Wednesday, February 28, 2007 12:05
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] Guestion about speedup mapguide,diferent
domainname to mapagent.fcgi.

Another theory that I am thinking about at the moment... what if one
makes a virtual web server folder out of the directory where tiles are
generated? This way tile pngs will be directly accessible via http
without going through either MapGuide's server or web  components, at
the cost of certain assumptions (one base layer group only in the map,
no changes to the map will be detected).