Re: Basic Question
Re: Basic Question
- Subject: Re: Basic Question
- From: Paul Lynch <email@hidden>
- Date: Thu, 23 Mar 2006 14:11:10 +0000
Yes, I was too lazy to double check what the actual parameter passed
to your app start up is, and used the same terminology as Chuck, we
all know what he meant :-).
I mostly develop using Xcode, as it comes out of the box; which means
that I use the standard WODirectConnectEnabled setting. But I am
very aware of what the differences are with that setting on and off.
Many people over the years have advised turning it off, as you do,
and for very sound reasons. Me, I'm just lazy, too lazy to bother to
turn it off, which works for me 95% of the time.
I reckon that "good enough" is good enough - which is why I use Xcode
(although I have come very close to switching to Eclipse), don't use
D2W, and didn't moan much about the change from ObjC to Java.
Paul
On 23 Mar 2006, at 13:05, Kieran Kelleher wrote:
Question (another basic one!) .... when you say the app serves the
resource in "dev mode", do you mean in "direct connect mode"? So
the question is if you are _developing_ in "deployment mode", aka -
DWODirectConnectEnabled=false, then does Apache not serve the
resource?
Regards, Kieran
On Mar 22, 2006, at 6:22 PM, Paul Lynch wrote:
On 22 Mar 2006, at 23:10, Chuck Hill wrote:
Hi Paul,
On Mar 22, 2006, at 2:56 PM, Paul Lynch wrote:
On 22 Mar 2006, at 22:45, Mark Morris wrote:
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.
Are you sure about that. Isn't it just another call to
WOResourceManager.urlForResourceNamed and not a trip through a
WORequestHandler? Yes, it is still overhead. Also, IIRC, the
app _does_ serve the image in development mode. That may be
confusing the issue. It is perhaps an argument in favour of not
using Web Server Resources as it creates a difference between
development and deployment.
Of course you are right - I have been confusing the issue by using
WOResourceManager and WORequestHandler interchangably, which they
are not.
And yes, the app serves the resource in dev mode - which I would
claim as yet another good reason not to use dev mode, rather than
a reason not to use Web Server Resources. It may be that older
versions of WO served resources themselves in deployment as well -
I have vague recollections of being shocked when I discovered
this, and quickly banned the use of Web Server Resources, but that
was a long time and several versions ago.
Paul
_______________________________________________
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