Talk:Tiles@home/RFC
2 - Login should be done via .htpasswd
Why use such a restrictive method (no direct link to a DB, not scalable, ...)? It's very possible to achieve the same result using PHP.
3 - store tiles in file system
I would be much in favour of storing the tiles in the filesystem, that's what filesystems are made for. Access should definitely be without any PHP interaction, i.e. configure Apache to find files where they are instead of executing (slow and resource hungry) PHP code for every single tile accessed. You would not need a complex directory structure, just splitting by digits would be fully sufficient (i.e. tiles/12/1234/5678.png becomes tiles/12/1/2/3/4/y5/6/7/8.png - the "y" inserted for disambiguation). This can be done by a simple regex-based rewrite rule in Apache, which I can provide if required. Another thing to keep in mind is the number of i-nodes available; make sure that you are on a file system actually capable of storing what you want to store. --Frederik Ramm 19:25, 18 February 2007 (UTC)
Come to think of it - I don't believe that 2^18 files in one directory should be a problem for modern file systems but I'll inquire. --Frederik Ramm 19:29, 18 February 2007 (UTC)
A simple test...
touch 0
for x in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
do
find . -type f|while read filename; do; touch ${filename}0; touch ${filename}1; done
done
... creates 2^18 files on a vanilla ext3 filesystem (Linux) without complaint. 2^18 directories shouldn't be a problem either. --Frederik Ramm 10:01, 19 February 2007 (UTC)
BOINC Project
Hi there, I would sponsor my CPU but the installation is very difficult for me. For distributed projects the BOINC platform is a quite easy way. Might it be possible to migrate Tiles@home? --!i! 08:03, 23 February 2009 (UTC)