| | 1 | = !MapGuide RFC 75 - Adding caching support to GETTILEIMAGE = |
| | 2 | |
| | 3 | This page contains an change request (RFC) for the !MapGuide Open Source project. |
| | 4 | More !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 | |
| | 22 | Currently the tile service has no support for http cache semantics. |
| | 23 | |
| | 24 | == Motivation == |
| | 25 | |
| | 26 | HTTP caching is a very simple way of increasing performance. |
| | 27 | |
| | 28 | Proxy servers cannot currently cache MapGuide GETTILEIMAGE responses, |
| | 29 | without custom configuration and overrides |
| | 30 | |
| | 31 | == Proposed Solution == |
| | 32 | |
| | 33 | Adding cache headers to tile service. |
| | 34 | |
| | 35 | This would require support adding the source tile timestamp |
| | 36 | to the HTTP header and then support returning 304's as required |
| | 37 | |
| | 38 | == Implications == |
| | 39 | |
| | 40 | None |
| | 41 | |
| | 42 | == Test Plan == |
| | 43 | |
| | 44 | TBD |
| | 45 | |
| | 46 | == Funding/Resources == |
| | 47 | |
| | 48 | TBD |
| | 49 | |
| | 50 | == Trac Tickets == |
| | 51 | |
| | 52 | [http://trac.osgeo.org/mapguide/ticket/467 Add proper cache headers & file date to GETTILEIMAGE response] |
