For example, I have 300 products, each product will have several images. And these images could be jpg, png, or gif.
I would use http to upload instead of ftp.
1) these files have to be in certain folders, such as I will put all the files for product# 3 in this folder, "productImages/3/". Use ftp the user not just have to switch to ftp sofware and also has to remember where to put these files. Too many troubles.
2) plus, in some cases, the ftp uploaded images may have the different ownerships and will not be able to auto delete by php later on.
My questions are
1) will http upload have some troubles if I move the scripts to another platform and say the server administrator may not allow the images folders to be set up as 777? I run into this case once, but it should be rare, just the "server administrator" (a reseller of hosting) doesn't know how to do it and i was not given the shell access to do it by myself. in simple words, http upload should be supported by most hosting platforms, right?
2) if I use http to upload images, should I at the same time, search the images folder for that product, serialized and save it in the database. When in the public interface to display the images of this product, I don't need to search for folder for images, I just need to grab images names from database. - the problem is that if someone ftp/shell delete images, or ftp upload images then there will be broken images links or missing images, because the ftp uploads/deletes will not be recorded in the database? so should I just search the folder each time I want to display images of a product instead?
Thanks!
