[mapguide-internals] Tile caching

[Zac Spitzer]

On Fri, Feb 29, 2008 at 4:48 AM, Jason Birch <Jason.Birch at nanaimo.ca> wrote:
> Hi...
>
>  I was just looking at Zac's recent ticket about adding cache headers to
>  GETTILEIMAGE requests.
>
>  https://trac.osgeo.org/mapguide/ticket/467
>
>  I don't think that this is the best way of presenting our tile caches.
>  Personally, I'd prefer to see a direct HTTP interface to the cache,
>  where the user requests a file from the webserver as a resource.  That
>  way all of the HTTP-goodness (cacheing, etc) is built-in.

Tilecache http://tilecache.org/ :)

Writing a mapguide rendering backend plugin for tilecache would
probably be the easiest effort wise. It
would require adding python into the mix, but it's a code base that is
already written and working
in production.

I think going if any changes in this area should adopt existing
standards or adopt existing patterns
where possible (GETTILEIMAGE and WMS feel a bit like indentical twins
separated at birth).

>
>  I don't think that this would be all that hard to do.  There would have
>  to be a 404 handler that either generates and sends back images that
>  don't exist or, if it is unable to generate the image send the
>  appropriate 400- or 500-level codes.  The only problem that I can see
>  with this is security.  There would have to be some way for either
>  MapGuide to use OS or LDAP security (and the web server to use the same)
>  or for the web server to use the MapGuide user store for authentication.
>
>  There was some discussion about MapGuide security earlier (at FOSS4G?)
>  and I certainly wouldn't be sad to see MapGuide's proprietary security
>  model replaced with something that tied into OS-level security.


>
>  Thoughts?
>
>  Jason
>  _______________________________________________
>  mapguide-internals mailing list
>  mapguide-internals at lists.osgeo.org
>  http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer -
http://zacster.blogspot.com (My Blog)
+61 405 847 168