Re: Basic Question
Re: Basic Question
- Subject: Re: Basic Question
- From: Mark Morris <email@hidden>
- Date: Wed, 22 Mar 2006 17:07:04 -0600
On Mar 22, 2006, at 4:56 PM, Paul Lynch wrote:
On 22 Mar 2006, at 22:45, Mark Morris wrote:
This thread is getting a little confusing, because there are at
least two different topics being discussed. ;-)
At least.
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.
This isn't strictly true - Web Server Resources have to take an
extra trip through a WORequestHandler in order to work out where
they live when the page is generated, although the actual serving
of the resource is handled by the web server. So there is some
overhead associated with using Web Server Resources, although it
isn't as much as some people may think. With a heavy load in mind,
I would try to minimise their use; but for most real world WO apps,
I personally don't feel a compelling argument against their use.
Paul
That's why is said isn't "really" an issue. ;-)
But doesn't WOResourceManager do caching of the paths to resources
it's already handled, so in most cases it's just spitting out the
path with no significant extra work? (Notice how I cover myself once
again with that "significant"!)
Regards,
Mark
_______________________________________________
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