I think she just wants to use a container to serve up the files and not have to worry so much about the details of sending files to a client. If they're inside of WEB-INF then, they aren't accessible via a URL -- something she wants, I think.
- Dave > -----Original Message----- > From: Michael McGrady [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 13, 2004 3:15 PM > To: Struts Users Mailing List > Subject: Re: Where Is the Best Place To Store Files? > > I know what Dave is saying you can do, and he is right, but ...... If > you store the files inside WEB-INF, you can still give all users > programmic access. The advantage in doing this is that you might find > in time that you need in the futrue to give some files limited access. > If they are inside WEB-INF, then you can do so easily. What I do is to > provide a resources directory under WEB-INF which holds all content > types with their separate directories by extention, e.g. > > WEB-INF > resources > gif > jpeg > jpg > pdf > ttf > > > And so on. > > Michael McGrady > > Durham David R Jr Contr 805 CSPTS/SCE wrote: > > >>If the uploaded files do not have to be protected (any > >>user can access them), where is the proper location to > >>store them? > >> > >> > > > >In this case, it looks like anywhere in your app except WEB-INF. Keep > >in mind that if your deployment process involves deleting your web-app > >and reconstructing (such as is the case with many war based deployment > >systems), then you could lose previously uploaded files. > > > > > >- Dave > > > >--------------------------------------------------------------------- > >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]
