Well, I have no clear idea of what you mean by "download area interface feature".
If it is about allowing file upload with PHP to add files in the download area with an interface, I guess that would be possible, despite the fact that's not a feature I'd like to see available at Gna! (web browser is probably the worst tool for file upload, not to mention the loss of ssh security) -- so it would have to be configurable. But I guess this would require to give apache write access and so this is not the second option you're thinking about.
Can you elaborate how would works this second option?
Do you plan to store in the database data sent and then get it written by a backend script? This could be indeed added, with not much work (a PHP page that allows adding entry in the db, a backend script that extra data and remove it when written). But I'm not sure of what it would implies for your SQL server (hum, what would happen if several persons upload several files of more than 2 MB at the same time... ?), especially in regard of scalability.
We did not though about file upload, although we could provide such feature (we could also store the file in a temporary writable directory). But that's not the goal of the project.
The problem is that currently, it is not possible to manage files at Savannah, due to the ftp.gnu.org-like upload schema.
So, we just want to provide an ergonomic way for user to create directories, rename/move/delete files, and create symlinks.
The second solution consists of storing planned changes (ie 'moving machin.zip to machin-1.0.zip' - not the files themselves) in the database, and have the cron job do the described changes. The interface should be able to show both the current download directory and the planned download directory (the one after the changes are done).
And we keep the ftp.gnu.org-like upload style.
Crystal-clear? :)
-- Sylvain
_______________________________________________ Savane-dev mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/savane-dev
