spaetz <[EMAIL PROTECTED]> writes: >> For finding clients a metadata xml file uploaded parallel to the >> tileset and deleted after some time would be sufficient. No need to >> keep that data forever ... > > I'd agree with it, but whoever implements, decides. That's how open > source works :-)
I'd rather not deal with XML. The information we want to convey is not that complex that we need a markup language like XML. A simple text file with lines of key: value pairs will do, IMHO. The question for me is more where the data should be included: 1. in the tileset file 2. in a separate file (can you upload two files in one HTTP POST?) 3. as HTTP POST variables >From the client standpoint I would prefer the first option. The uploader would not need to care at all about this data. It would simply grab every tileset file it finds in uploadable and push it to the server. The uploaded data would only consist of username, password and the tileset file. No need to parse anything at all. And no need for mile-long file names. The server would only need to store the file in its incoming directory and maybe stick the upload username to the end of it. No need for any database access at all (Don't know how the server is currently storing meta info for uploaded zip files). What information do people want to see on the tile details pages? All this could be stored in the tileset file. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
