I saw the upload to folder option in the configs and was wondering what it was for. What's the envisioned usage for that option? Will one client be able to handle uploads from multiple other clients (currently 6 w/ a total of 11 CPU cores for me, but will be more soon) at the same time? I'd think that when the queue gets backed up on the server and we're stuck with 600 second retries that the client tasked with the uploads would fall behind very quickly. Possibly to the point of exceeding the 1.5 hour retry limit. Is the "upload client" expected to just be a regular client running in loop mode, or is there a special mode for the client that will be handling uploads?
Sorry for all the questions, it sounds like a neat feature for those of us with small farms of machines, but I'm not clear on what the exact usage should be. The API changes should help out quite a bit. The inkscape preferences problem is still annoying, but I've fixed it on my machines by setting the folder to read-only so inkscape can't kill it if it crashes. This seems to work well for now since I don't use inkscape for anything else. I had a client make it over 1900 consecutive loops before crashing the last couple days, so I guess that means the client is getting much more stable than it used to be. -Jeremy ----- Original Message ----- From: "Dirk-Lüder Kreie" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, December 11, 2007 9:29 AM Subject: [Tilesathome] New features of the [EMAIL PROTECTED] client -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since there has been some time since I last updated what went on coding the client I'll do a new update about what has happened recently in client development. I'm not going to catch up every change since my last update on the topic, just what I can think of that might be of interest. For detail check the trac svn history of the client[1] The current version is revision 6022, still called "Oslo" It supports uploads to a directory (check sample config) instead to the server. This is intended for multiple clients that run on one or more computers connected via LAN or similar where only one [EMAIL PROTECTED] process gets charged with the upload to the world. If you run multiple clients on one host be sure to give each instance it's own working directory! Secondly a delay has been introduced. A failed API connection results in a delay of 60 seconds, a second failure in 240 seconds and exponentially growing to just over one hour (to a total delay of about 1:30 hours or something) The delay will be tweaked based upon future experience. (Thanks go to "Milenko" for the patch used as a basis for this behaviour) Also the client now prints a warning in xy mode if the zoom level has been omitted. [1] http://trac.openstreetmap.org/changeset/6022?new_path=applications%2Frendering%2FtilesAtHome - -- Dirk-Lüder "Deelkar" Kreie Bremen - 53.0952°N 8.8652°E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHXp7CFUbODdpRVDwRApHiAKCiqAY+EC9wwMlIbgnFLUxwpBZjgwCgsuRn bL61KmO8P/gvA8ioqfo+O/c= =vANi -----END PGP SIGNATURE----- _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.17.0/1180 - Release Date: 12/10/2007 2:51 PM _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
