|
Were you just paraphrasing what I said or was there an alternate point ?
:-)
Regards,
Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
-----Original Message-----
message: 4
date: Sun, 01 Mar 2015 20:53:16 -0600
from: Booth Martin <booth@xxxxxxxxxxxx>
subject: Re: Storage of Images (use in web pages)
If security for the images are an issue then it is probably more
effective to point the security at the page and its links rather than
the image itself. If it is a page serving up secure badge ID photos,
for instance, probably non-eligible people should be kept from accessing
the page itself.
On 3/1/2015 7:57 PM, Richard Schoen wrote:
For web sites, images in IFS directories and opened up publicly viaApache for a web site are fine if part of the site itself.
files if they are secure documents such as those part of a document
Ex URL: http://1.1.1.1/images/test.gif
Could point to IFS folder /www/apachedft/htdocs/images/test.gif
You need to use CGI or some other application driven method to return
management system or secure file access system.
secure documents pointers are stored in the database.
For public images pointers are relative paths to a website folder. For
Your DB will also swell if you have a large number of blobs being managed.
Blobs are a pain to manage and probably for super-secure apps only.
I don't normally recommend this approach.
NFS, SAN.
Better to store metadata in a DB and docs in file system such as IFS,
HelpSystems
Regards,
Richard Schoen | Director of Document Management Technologies,
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
_______________
Confidentiality Notice: This e-mail, including attachments, may include
confidential and/or proprietary information, and may be used only by the
person or entity to which it is addressed. If the reader of this e-mail is
not the intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of this
e-mail is prohibited. If you have received this e-mail in error, please
notify the sender by replying to this message and delete this e-mail
immediately.
________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.