spaetz <[EMAIL PROTECTED]> writes: > On Wed, Aug 06, 2008 at 11:45:20PM -0400, Matthias Julius wrote: >> Dirk-Lüder Kreie <[EMAIL PROTECTED]> writes: > >> >> Sure, this could be the next step. But, for all of this to be >> >> useful, the server needs to do something with that ID. How many >> >> clients upload through an uploader? > > One reason why the renderer id could be useful is that the server > could then check that no client id has more than 1 job ongoing. This > is (still possible but) a little trickier when the uploading id > differs from the job taker. but thanks for implementing. we'll make > good use of it, I'd think.
A limit of 1 might be a bit low. First, the upload process can be forked and in the case of a dedicated uploader a new job will likely be requested before the old one has been uploaded. Then, there might be reasons why a client can not return the job to the server, a power failure for example. > >> > I know mine do, but I also use UseHostnameInZipname=1 so it's >> > still identifiable which client rendered what. >> I didn't think the server gets to see the filename of the zip file. >> Am I wrong? > > mmh, actually it does. It stores the file under the same name as > upladad (appending underscores if the name exists already) in the > Incoming' directory and the name is stored in the 'uploads' db as > well.. But the server doesn't care about which name it is or makes any > use of it. All it iis interested in, are the filenames of the unzipped > file, as they give away layer, and z,x,y. That's good. I had the impression from old tile2.php that didn't use the original filename. It would then be easy to let users define a client name in tilesAtHome.conf to be included in the filename for easy identification of several client running on the same machine. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
