On Fri, Jul 11, 2008 at 06:53:13AM +0200, spaetz wrote: > Lower priority items: > - Reimplement tileset complexity measure.
As an idea concerning the complexity measure - Could the number of
objects be simply used? E.g. the client downloads the data via the api
and simply counts points and ways e.g:
grep "<node" | wc -l
This should somhow correlate with time and memory usage while rendering
and is not subject to some arbitrary interpretion.
Also clients could one day build some strategy on what to announce as
maximum complexity they are capable to render - starting low and
increasing until a fail - E.g. tcp slow start - increasing the window
on success and shorten it on fail..
Or the client could interpolate on the found memory on what complexity
it should be able to handle on that hardware. Or the user could try
to limit to a specific amount of memory.
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
signature.asc
Description: Digital signature
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
