On Fri, 04 Oct 2002 10:38:20 -0400, Jerry Johnson wrote: > MySQL will be more than sufficient. > > 250,000 images, 250 or so weekdays, that is on average 100 images per day. > > Depending on the number of users into the system at a time, you probably could get >by with Access. I wouldn't if you can use anything else, but you probably could.
Not that many. Possiby 5 max. > As for the storage, I would say do not store the images in the db, just the links. Thats what I thought. > I would suggest, however, that you do not store the images in a single directory. >Come up with a good file nameing convention, including directory structures. Maybe >something like YYYY/MM/DD/YYYYMMDD00000.tif This naming convention would occur before the FTP to the server. Just change the remote filename during the FTP? Can the creation of these directories happen automatically? > I would also keep a copy of the original tif file, as well as the edited version >made available. But store it offline, or reachable only by a CF call, rather than in >the wwwroot tree. Same goes for all the image, I guess. Just so no one can go directly to an invoice by knowing your naming convention. Us a cf program and cfcontent to return the images, rather than direct links to the files. Whats the purpose of this? > > What image format are you going to serve up? I might suggest sticking the tifs into >a pdf for display. Ghostscript can do this with a simple cfexec call. I thought of that but its possible the image on the server could require editing. I want to make this painless as possible. More like a "Upload for Dummies". :-D > > I might also suggest backing the images up regularly in a permanent way. All images would be archived to CD monthly. > Sounds like a fun project. Good Luck Thanks. > Just some rambling thoughts. > Jerry Johnson > > > > >>> [EMAIL PROTECTED] 10/04/02 10:04AM >>> > Hello, > > I posted this question a few weeks ago but have found out more information since >then. I want to do it in CF. I was told I can use any OS and databases I want. > It does not have to be Access (like before). They want the process streamlined. >Presently, this is how its being done. > > 1. User scans invoices into .tif format and ftp's the graphic file to a repository >on the server (off-site. ISP). > 2. They then log into the website. Click on the graphic file which opens a template >with fields and the graphic below. They enter in invoice#, company etc. which I >assume, > gets stored into a database. > 3. If an image (invoice) has pricing that they don't want a customer to see then >they open up the "master" image. Edit the graphic and remove what they need and then >ftp the > file back to the server again. > > I just found out there will be approximately 25,000 images posted yearly. Even is I >use SQL wouldn't it be best to have links in the database pointing to the directory >and files > rather than include the binary data into the database? > > Would mySQL be sufficent. I would think as I've been told many times before that >Access is not sufficient but I'm just want clarification. I have the go ahead to get >an ISP and I > don't want to screw this up. SHould it be windows or u*x based? > > Your thoughts wonderful guru's!!!!! > > > > --------------------------------------------------- > Colonel Nathan R. Jessop > Commanding Officer > Marine Ground Forces > Guatanamo Bay, Cuba > --------------------------------------------------- > > > > > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
