About this ´a fallback mechanism to display "legacy tiles" if we had no tile yet, allowing for a slow switchover. converting just takes quite a while.´
Does it put those legacy tiles also in the render queue, so it will get rendered whenever a client needs work to do -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens spaetz Verzonden: vrijdag 11 juli 2008 6:53 Aan: Ian Dees CC: TilesAtHome Onderwerp: Re: [Tilesathome] Cutover to new server? When? On Wed, Jul 09, 2008 at 11:33:59AM -0500, Ian Dees wrote: > Just saw a bug: > > Someone was able to make a request for tile 4097,4097 z12, which caused a > "Coordinates out of bounds (0..4095)" error and exit on my client. It was no bug, just a feature that happened to not be implemented yet. :-) Fixed now, it's impossible to request invalid coordinates now. > Also, is the "put tileset back to server" implemented on the server side > yet? Nope, nothing of this sort is done yet. It's still the simple hand out and forget model. As a first step, I'd like to rerequest active requests that haven't been returned for -say- 10 hours. But I would like to collaborate with deelkar tp get a proper feedback thing running where a clien could say every 2 h or so "i'm still working on it",or coul return it back to the server with a reason (API down, tileset too complex, etc). I have to admit that I have no clue how the client currently tells the server about errors. On the plus side, I implemented some things yesterday: - automatic requesting of changed tiles is enaabled every hour now - a fallback mechanism to display "legacy tiles" if we had no tile yet, allowing for a slow switchover. converting just takes quite a while. - Munin stats of the new [EMAIL PROTECTED] server are implemented and online now. - no more ugly gaps in the static map browser Next on my todo list: - Prevent duplicate requests. This is still possible ATM, so the same request could be handed out to several clients. (uploading a layer will satisfy all outstanding requests though). Pending/fulfillled request stats will only start to make sense, once this is in. - Reimplement MapOf or try to integrate the existing PHP version at the current location. Don't know how to do yet. - Implement dead-simple re-requester on failure first. Work on a more elaborate feedback/error mechanism next. Lower priority items: - Reimplement tileset complexity measure. - Actually save the user id who uploaded a tileset in the tileset file - Make the lowzoom tile stitcher automatically run on updated tilesets. Right now a complete run takes 2 days. - Nicer user statistics page spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
