Changes between Initial Version and Version 1 of MapGuideRfc75


Ignore:
Timestamp:
Jul 7, 2009 8:18:56 PM (9 years ago)
Author:
zspitzer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc75

    v1 v1  
     1= !MapGuide RFC 75 - Adding caching support to GETTILEIMAGE =
     2
     3This page contains an change request (RFC) for the !MapGuide Open Source project.
     4More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     5
     6
     7== Status ==
     8
     9||RFC Template Version||(1.0)||
     10||Submission Date||()||
     11||Last Modified||(Zac Spitzer) [[Timestamp]]||
     12||Author||(Zac Spitzer)||
     13||RFC Status||(proposed)||
     14||Implementation Status||()||
     15||Proposed Milestone||(2.2)||
     16||Assigned PSC guide(s)||(when determined)||
     17||'''Voting History'''||(vote date)||
     18||no vote|| ||
     19
     20== Overview ==
     21
     22Currently the tile service has no support for http cache semantics.
     23
     24== Motivation ==
     25
     26HTTP caching is a very simple way of increasing performance.
     27
     28Proxy servers cannot currently cache MapGuide GETTILEIMAGE responses,
     29without custom configuration and overrides
     30
     31== Proposed Solution ==
     32
     33Adding cache headers to tile service.
     34
     35This would require support adding the source tile timestamp
     36to the HTTP header and then support returning 304's as required
     37
     38== Implications ==
     39
     40None
     41
     42== Test Plan ==
     43
     44TBD
     45
     46== Funding/Resources ==
     47
     48TBD
     49
     50== Trac Tickets ==
     51
     52[http://trac.osgeo.org/mapguide/ticket/467 Add proper cache headers & file date to GETTILEIMAGE response]