• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Basic Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Basic Question


  • Subject: Re: Basic Question
  • From: Paul Lynch <email@hidden>
  • Date: Wed, 22 Mar 2006 23:22:28 +0000


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


  • Follow-Ups:
    • Re: Basic Question
      • From: Kieran Kelleher <email@hidden>
References: 
 >Re: Basic Question (From: Jean Pierre Malrieu <email@hidden>)
 >Re: Basic Question (From: Jeffrey Pearson <email@hidden>)
 >Re: Basic Question (From: Andrew Satori <email@hidden>)
 >Re: Basic Question (From: Mark Morris <email@hidden>)
 >Re: Basic Question (From: Paul Lynch <email@hidden>)
 >Re: Basic Question (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Child EditingContext and fetches
  • Next by Date: Including Pre-existing Assets (was Re: Basic Question)
  • Previous by thread: Re: Basic Question
  • Next by thread: Re: Basic Question
  • Index(es):
    • Date
    • Thread