| | 1 | = !MapGuide RFC 112 - sqlite based tile cache = |
| | 2 | |
| | 3 | This page contains a 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||(Date / Time submitted)|| |
| | 11 | ||Last Modified||(your name here) (modification date here)|| |
| | 12 | ||Author|| Zac Spitzer || |
| | 13 | ||RFC Status||(draft)|| |
| | 14 | ||Implementation Status||(pending)|| |
| | 15 | ||Proposed Milestone||(2.3)|| |
| | 16 | ||Assigned PSC guide(s)||(when determined)|| |
| | 17 | ||'''Voting History'''||(vote date)|| |
| | 18 | |
| | 19 | == Overview == |
| | 20 | |
| | 21 | This is a proposal to implement a secondary tile cache persistance layer using a sqlite db. |
| | 22 | |
| | 23 | == Motivation == |
| | 24 | |
| | 25 | The file base tile cache can be problematic for backup or copying due to the massive number of files and directories.[[BR]] |
| | 26 | |
| | 27 | A single sqlite db file per tile cache solves this problem. [[BR]] |
| | 28 | |
| | 29 | Generating tiles is currently done using a rather brute force approach, by storing[[BR]] |
| | 30 | tiles in a database, it can be queried for existing tiles and only missing tiles[[BR]] |
| | 31 | can be requested. |
| | 32 | |
| | 33 | == Proposed Solution == |
| | 34 | |
| | 35 | Implement sqlite based persistance as an option for the tile cache. |
| | 36 | |
| | 37 | Add additional API methods to the tile service to query and manage the tile cache (TBD)[[BR]] |
| | 38 | |
| | 39 | Some way to convert between tile cache formats (standalone util?) |
| | 40 | |
| | 41 | == Implications == |
| | 42 | |
| | 43 | TBD |
| | 44 | |
| | 45 | == Test Plan == |
| | 46 | |
| | 47 | Existing Tile Cache unit tests still apply |
| | 48 | |
| | 49 | == Funding / Resources == |
| | 50 | |
| | 51 | Ennoble |
| | 52 | Community(?) |
