May 1st, 2010, 10:02 AM
Hah - it's possible this may become a higher priority. A rather high-profile client has expressed a need for a slew of tougher security, some of which lend themselves to being introduced to the core. Looks like this may prove to be a short-term goal, but we'll see how it goes.
Regarding your comments, I agree that baby steps are better than none. I tend to take on the programmer's mindset for problems in that they should be solved *completely*, but security measures aren't like that. For the storing the files outside of the webroot, yes, Form Tools would need to copy them into a temp folder within the webroot to allow download - or at least dynamically stream the content for downloading by the browser. I can see why this would be handy, but I think it'll end up lower priority.
Anyway, good speaking. I'm going to be making it more transparent what is being worked on in each version. Right now people can only find out exactly what's been worked on after each release [http://docs.formtools.org/changelog.php], which isn't much use. I'll make a post when that page is up and running.
Speak soon!
- Ben
Regarding your comments, I agree that baby steps are better than none. I tend to take on the programmer's mindset for problems in that they should be solved *completely*, but security measures aren't like that. For the storing the files outside of the webroot, yes, Form Tools would need to copy them into a temp folder within the webroot to allow download - or at least dynamically stream the content for downloading by the browser. I can see why this would be handy, but I think it'll end up lower priority.
Anyway, good speaking. I'm going to be making it more transparent what is being worked on in each version. Right now people can only find out exactly what's been worked on after each release [http://docs.formtools.org/changelog.php], which isn't much use. I'll make a post when that page is up and running.
Speak soon!
- Ben