From: Anthony D'A. <aa...@dr...> - 2006-12-10 18:42:15
|
> it has horrible management of files, especially filenames, theres no > correction of invalid names or names that could be problematic and i'm > tired of having to kill runaway ids processes from uploads gone bad, > wether it be uploads that are cancelled on the user end and never > die on > the ids end or if the user gave it a filename that ids cant hang > with.. Hmmm, I've never tried uploading files straight to IDS. The thing that most attracted me to IDS in the first place was the fact that I *didn't* have to do this, that I could just SCP the files into place, create directories, move them around etc. arbitrarily and IDS would do the right thing. I looked briefly at Gallery a while back, and it really really didn't meet my needs. It insisted on keeping images in some monolithic db where I couldn't get at them or manage them from the shell. I have two issues with IDS: 1) Thumbnail generation doesn't work on TIFF files 2) Speed. Even with some of the patches that came across this list, IDS is waaaaay slow. My server is very lightly loaded and it should be able to be snappier at scaling images. The Image:Info calls to read embedded JPEG/JFIF comments appear to have been written by a deranged wombat, and are thoroughly broken, as I've posted here in the past. After spending hours trying to come up with a better solution, I gave up and replaced it with a call to rdjpgcom, which of course is less than speedy itself to fire up an external process. |