From: blaine <bl...@al...> - 2003-04-03 20:49:03
|
On Thursday, Apr 3, 2003, at 12:34 America/Vancouver, Mike Traum wrote: > FTP would work for me, it just seems odd. I believe that any hosting=20= > site=A0that accepts file uploads would accept unlink (with the=20 > modifications I mentioned in a previous post). > > But, whatever. I'll make the modifications. Right now, the=20 > modifications I have on my list for the 'admin' to be release quality=20= > are: > - remove username & password from config & use ftp to write/delete=20 > files > - make 5 fields for simultaneous calendar upload > - change delete dropbox into checkboxes so multiple ones can be=20 > deleted in one step > - remove javascript confirm > > That sound right? If so, I'll have that done tonight. Would you prefer=20= > a patch off of the original, or off of the current cvs? The current source is working beautifully on my server, after tweaking=20= the permissions a little bit on the calendars directory. If FTP support=20= is to be added, it should be done as an option, not to replace the=20 current system. Also, if it's not too much trouble, factoring out the=20 actual upload code should allow for FTP or WebDAV uploads. I think that WebDAV is important, not only because Apple is moving=20 towards it, but because it supports operation over HTTPS. Anyone trying=20= to run a secure server (e.g., someone who's disallowed 'unlink' in=20 php.ini) should *not* be using a plaintext FTP server. Since there's no=20= real standard for sFTP (ssh, ssl-tunneled ftp, etc), WebDAV is really=20 the best protocol to standardise on, imho. Thanks, Mike! b. |