Re: Including Pre-existing Assets (was Re: Basic Question)
Re: Including Pre-existing Assets (was Re: Basic Question)
- Subject: Re: Including Pre-existing Assets (was Re: Basic Question)
- From: Paul Lynch <email@hidden>
- Date: Thu, 23 Mar 2006 08:18:44 +0000
On 22 Mar 2006, at 23:57, Jeffrey Pearson wrote:
The little light turned on for most of this. Except for 2b:
or b) add it to the project in the application server target and
use the WOImage tag if I want the app server (ie Webobjects or
Tomcat) to serve it up (understanding a slight performance
penalty is applied).
No. You can add it to the Web Server target only; its location
will be resolved by the WOResourceManager/WORequestHandler, and
served by the web server.
Why would I be adding it to the Web Server target scope if I wanted
it to be served from the Application Server? Wouldnt I then be
telling the project the the image is going to be found in my HTTP
server and not the webobjects application server?
Because filename bound images are not served from the app server
(except in some strange circumstances referred to earlier). The
image is indeed to be found, after proper installation of your
project, on the web server.
If you want to serve an image from the app server, use the data
binding, and create some method to provide your image as a data
object. Using the app server to provide images has a high overhead
and should be discouraged for most purposes, IMHO; it is only
reasonable that the developer should be forced to make a little more
effort in this case. The data binding is most appropriate when the
resource is fully dynamic, ie, generated on the fly inside your app.
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