Pitney Bowes MapXtreme - Manual (Page 97)

Chapter 5: Web Applications, Controls, and Tools
MapXtreme Tile Handler
MapXtreme v7.1 97 Developer Guide
Caching
The MapXtreme Tile Handler supports caching of frequently used tiles so that application
performance does not suffer. Caching instructions are included in the web.config file following
Microsoft’s.NET Framework
HttpCacheability .
Five types of caching (plus a no cache option) are supported. These enumerated values are used to
set the Cache-Control HTTP header.
TileServer The path to your instance of the MapTiling handler.
This must match the beginning of the "path" entries
in the "httpHandlers" section of your web.config.
See above.
mapname The name of the map on the Tile Server.
level The level of requested tiles. Zero-based.
x;y The x and y ordinates of the requested tile (zero-
based).
For example, at level 3 the map consists of 64 tiles
in 8 rows and 8 columns. The x and y arguments for
the upper left tile would be 0;0. For the lower left
tile, it would be 0;7.
ext An extension denoting the format of the tile (e.g.,
.gif, png). Must match a supported format.
Argument Description
NoCache Sets the Cache-Control: no-cache header. Without a field name, the
directive applies to the entire request and a shared (proxy server)
cache must force a successful revalidation with the origin Web
server before satisfying the request. With a field name, the directive
applies only to the named field; the rest of the response may be
supplied from a shared cache.
Private Default value. Sets Cache-Control: private to specify that the
response is cacheable only on the client and not by shared (proxy
server) caches.
Public Sets Cache-Control: public to specify that the response is cacheable
by clients and shared (proxy) caches.