Re: Basic Question
Re: Basic Question
- Subject: Re: Basic Question
- From: Mark Morris <email@hidden>
- Date: Wed, 22 Mar 2006 16:45:54 -0600
This thread is getting a little confusing, because there are at least
two different topics being discussed. ;-) But I would like to make
sure there isn't confusion about images and other "web server
resources", and really just reiterate and summarize what Jean Pierre
has already said.
Images and the like can be kept in some static location, such as
{document root}/images/, as is suggested below. However, they may
also be kept in the "Web Server Resources" group within your
project. Either way, the web server will be handling requests for
the image, not the WebObjects application, so performance isn't
really an issue.
Keeping an image in a central, static location might make sense for
something shared by more than one application or with static pages,
such as a company logo. Keeping images and such with the project has
advantages for versioning and localization (and perhaps others, but
that's all that comes to mind).
Regards,
Mark
On Mar 22, 2006, at 4:14 PM, Andrew Satori wrote:
Maybe I can help.
WebObjects isn't really efficient at serving static content, so
it's more efficient to host the static content, like images,
outside the deployment war of our WebApp, thus you WO application
might live in cgi-bin/WebObjects/WOApplciation.woa your static
content lives in /Library/WebServer/Documents/images/ and is
referenced from within your WOApp as /images/imagename.jpg. This
let's Apache do what it does best and WO do what it does best, but
presents the same.
In my case, and from what I can tell of most WO Apps, the entry
point to the app is an html redirector that loads the WOApp
For example, I have on the webserver in /Library/WebServer/
Documents/ an index.html as well as a css folder for the css files,
and an images directory for images and a scripts directory for the
common included .js files (for client side DHTML behaviors).
Index.html is nothing more than short page that contains a little
descriptive text and a manual redirector for that 1% of user for
whom the META redirect fails for. Then, within the WOApp, all
references to the static content on the site are given absolute
paths without the host (css file is ="/css/default.css"). What this
means is that the JSP 'all in a WAR' deployment doesn't work, but
it also means that the static content isn't running through the
adapter jacking up the load on the less efficient Jasper or WO
adapters.
I hope this helps clear things up. I'm fairly new to WO myself, so
I might have this a little inaccurate, but I think I'm on sound
ground here based upon exploration of prominent WO based sites
(.mac and store.apple)
Andy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden