[Tilesathome] Processing delays

[Dirk-Lüder Kreie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Milenko schrieb:

> It would mean a little more work for the server when handing out work units, 
> but couldn't the server require the client to send username and password 
> when the client requests (just like it does to upload), and then like you 

That would request a POST as sending it in a GET every user on dev would
be able to read every password plaintext from the apache logs.

> said, the server could keep track of what active tileset belongs to which 
> client.  When the client connects again to request another tile, the serve 
> would just have to check and see if there are already x number of actice 
> tiles that belong to that client.

currently there is a possibility that a tileset is handled by multiple
clients, one would need to take that into account probably.

> Even a fairly high number like 10 or 20 would keep misbehaving clients from 
> sucking down huge numbers of tiles.

Agreed, for that you would indeed need some sort of authentication.

> According to the stats from yesterday there were ~130,000 requests for 
> renderings and only ~56,000 of those were actually uploaded.

There are still problems with a lot of tiles that only can render on
machines with 2 GB of RAM (or more).

- --

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

iD8DBQFHHOijFUbODdpRVDwRAnr2AJ9umTN/QCtrQxzGSQ8Vno6Fcpms2wCaAmAv
06YFJFtZzDeb2RYP26WvoTg=
=mysz
-----END PGP SIGNATURE-----