Changes between Initial Version and Version 1 of MapGuideRfc64

May 7, 2009, 9:16:25 PM (13 years ago)



  • MapGuideRfc64

    v1 v1  
     1= !MapGuide RFC 64 - Enabling strict exception handling for tile generation =
     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.
     7== Status ==
     9||RFC Template Version||(1.0)||
     10||Submission Date||(08.05.2009)||
     11||Last Modified||(UV Wildner) [[Timestamp]]||
     12||Author||(UV Wildner)||
     13||RFC Status||(draft)||
     14||Implementation Status||(discussion needed)||
     15||Proposed Milestone||(2.1)||
     16||Assigned PSC guide(s)||(when determined)||
     17||'''Voting History'''||(vote date)||
     22||no vote||||
     24== Overview ==
     26Currently an exception thrown during the stylization code for a tile is caught and ignored.
     27This can lead to partially incomplete tiles which are hard to detect as no error information is passed via the API.
     28Even worse the tile is kept in the tilecache!
     30== Motivation ==
     32Originally, the mapguide server has been designed as an interactive map generation system.
     33For the important use case of rendering tiles and filling the tile cache incomplete tiles are undesirable.
     34in particular keeping the faulty tile in the cache seems the wrong way to go.
     36== Proposed Solution ==
     38A switch in serverconfig.ini should be introduced which can change this behaviour on demand.
     40HandleRenderingErrors = STRICT
     42which leaves us room for additional ways to deal with this:
     44=== render a tile with an error message could be ===
     46HandleRenderingErrors = SHOW
     48=== default cases ===
     50HandleRenderingErrors = IGNORE
     52HandleRenderingErrors = DEFAULT
     54HandleRenderingErrors =
     56and ommitting the parameter would change nothing
     58However I think letting the tile into the cache should be generally prohibited in an exception situation.
     60== Implications ==
     64== Test Plan ==
     66Render tiles on a low memory virtual machine which causes memory errors and compare TileCache with different settings
     68== Funding/Resources ==
     71== closed Issues ==
     75== open Issues ==
     77Does anyone wants to have faulty tiles in the tile cache?