[OSM-dev] tiles at home job queuing... 2600

[OJW]

On Sunday 26 November 2006 00:12, you wrote:
>      "http://osm.bandnet.org/tilesathome/?job",

I've been experimenting with some other options for supplying requests:

http://osmathome.bandnet.org/Requests/?help

That's a module-based system, i.e. there are N different strategies for 
generating requests, each of which is stored in a separate file somewhere.  A 
module is picked at random to handle each request.

Each module might implement a different strategy, like:
* grow data from an existing area
* pick jobs from a queue
* refresh old tiles
* look at RSS feed for places people are editing
* look at planet.osm.diff for new places
* tiles marked as "need update" by people browsing
* popular tiles 
* oldest most interesting tiles

Since they're all in separate files, different people can be making changes in 
various modules without overwriting each other.  

We can then adjust the weighting of strategies depending on the situation, 
e.g.
* creating data for the first time
* gradual updates (normal use)
* replacing existing data (e.g. new rendering rules)

(Currently there aren't many modules, and they're not high-performance. That 
will change)

Regards

OJW

p.s. Might be worth sending x,y,zoom to the "finished" script rather than 
JobID, (it can look-up the job id from that information) since then it can 
mark jobs as finished even if the client got its tileset request from some 
other method

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20061127/42b8250d/attachment.pgp>