Why not have have your httpd serve the static content and leave the application to be handled by your app server (if you have this configuration).
This is what the httpd was designed for :) This gives you the independence of leaving your static content to reside on a disk server (or seperate box etc) and the application code to live inside the app server which can be deployed to without effecting the static content. Chris McCormack -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 14 October 2004 09:49 To: [EMAIL PROTECTED] Subject: RE: Where Is the Best Place To Store Files? Hi, guys. Calm down a bit. The original question never said that these files need to be uploaded by the client, or did I miss that bit? All I know is there are readonly files that need to be served via HTTP without access restriction and are already there at deployment time so a database is not the option to store them. And the superior said a database is not the option to store them. If it's just static content, the answer has already been given: place it anywhere inside the webapp but outside WEB-INF. The rest is speculation. Hiran ----------------------------------------- Hiran Chaudhuri SAG Systemhaus GmbH Elsenheimer Straße 11 80867 München Phone +49-89-54 74 21 34 Fax +49-89-54 74 21 99 > -----Original Message----- > From: Michael McGrady [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 13. Oktober 2004 21:42 > To: Struts Users Mailing List > Subject: Re: Where Is the Best Place To Store Files? > > Durham David R Jr Contr 805 CSPTS/SCE wrote: > > >I personally opt to store uploaded files outside of the web-app's > >file-system altogether. This has to do with how easy it is > to serve up > >content with Java (and other languages, I'm sure) and the need to > >physically separate the application's persistent data from the > >application code. This has to do with deployment and backup > processes, > >though. > > > > > >- Dave > > > > There is a lot of sense in doing this, as well. > > > I don't do it and opt for inside WEB-INF because of business > reasons having to do with operating system independence that > are special requirements. This might be your most sensible > option. I am fairly clear in my mind that, if you have gone > far enough to use a framework like Struts, that you don't > want to expose any resources outside your control. Others, > maybe Dave, would disagree, and maybe they are right. > > Michael McGrady > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *********************************************** This e-mail and its attachments are confidential and are intended for the above named recipient only. If this has come to you in error, please notify the sender immediately and delete this e-mail from your system. You must take no action based on this, nor must you copy or disclose it or any part of its contents to any person or organisation. Statements and opinions contained in this email may not necessarily represent those of Littlewoods. Please note that e-mail communications may be monitored. The registered office of Littlewoods Limited and its subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB. Registered number of Littlewoods Limited is 262152. ************************************************ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
