[mapguide-internals] Please review RFC 107

Zac Spitzer zac.spitzer at gmail.com
Wed Jul 28 08:56:43 EDT 2010


what if RFC 107 returned a list of tiles which RFC 90 generated?

(assuming random seeding?)

On 28 July 2010 22:16, Trevor Wekel <trevor_wekel at otxsystems.com> wrote:

> I agree with Zac.  Tile generation should be implemented as a server-side
> batch process.  The proposed GenerateTile could be used to implement the
> rendering portion of that process.  Exposing it over HTTP is not really
> required.  Using a client application to continuously monitor a server-side
> batch process is a bit strange.  The server should just generate a log from
> the tile generation process and allow the client to grab the log whenever
> required.
>
> A server-side GenerateTile implementation is definitely required but it is
> only a small part of a much larger solution.  RFC 107 would likely take a
> day to implement since the tile generation process is already in place.
>
> RFC 90 Meta Tiling increases tile generation performance by an order of
> magnitude.  This work should be completed before implementing any new tile
> generation mechanism.  In other words, the server-side batch process should
> make heavy use of RFC 90.
>
> Once RFC 90 is in place, an enhanced Tile generation RFC could expose a
> GenerateTiles API which takes an extent and a scale.  Each API call would
> queue an area for rendering.  A serverconfig.ini parameter could be used to
> control the number of worker threads allocated to the rendering queue.
>
> Additional APIs could be introduced to display the current state of the
> Tile generation queue and return the log from previously completed
> GenerateTiles calls.
>
> Regards,
> Trevor
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
> Sent: July 28, 2010 1:31 AM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] Please review RFC 107
>
> Currently I believe the tile service simply returns success even when
> rendering fails
> and the incomplete result of the rendering is persisted as a broken tile
>
> Whilst returning a tile is some overhead, I would prefer to see more of a
> batched
> approach to seeding tiles. Requiring a single call per title is rather
> inefficent
> and chatty
>
> z
>
>
> On 28 July 2010 16:29, Ted Yang <ted.yang at autodesk.com> wrote:
>
> > Hi all,
> >
> > Would you please review RFC 107: Enhance Tile service to add a new API
> > GenerateTile.
> > Link: https://trac.osgeo.org/mapguide/wiki/MapGuideRfc107
> > Thank you.
> >
> > Best Wishes,
> > Ted Yang (Yuanyuan Yang)
> > Reeses,Tel: (8621)3866-4595
> >
> >
> >
> > _______________________________________________
> > mapguide-internals mailing list
> > mapguide-internals at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> >
>
>
>
> --
> Zac Spitzer
> Solution Architect / Director
> Ennoble Consultancy Australia
> http://www.ennoble.com.au
> http://zacster.blogspot.com
> +61 405 847 168
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>


-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168


More information about the mapguide-internals mailing list