Re: Application front door URL

Yes, indeed.

Note also that there is really no way for the application to know  
what is the "correct" web server name for all possible  
configurations, as the application server may well not be the web  
server host.

Sometimes I have supplied the web server name through the Java  
Properties system.

Paul

On 21 Feb 2006, at 11:24, Patrick Middleton wrote:

> This is true even if you're not using JavaMonitor or Monitor.   
> Those apps are used for editing configuration which gets pushed to  
> wotaskd.  The Apache DSO (or equivalent module for other HTTP  
> daemon) may take configuration from wotaskd or a similar  
> configuration from eg a file.  Either way, the "front door URL"  
> will need to include the application name, not the Application  
> executable's filename, and as previously stated these need not be  
> the same, and the application would need to discover that  
> information the same way that the Apache DSO does.
>
> The approach Paul suggests is the way to go if you need to parse  
> the request URL to discover applicationName etc; I generally don't  
> need this, and can get everything I want from the HTTP headers.
>
> If you need this outside of the request/response loop, the way to  
> do it is to cache it while still in the request/response loop,  
> possibly loading your cache by overriding appendToResponse(,).  [I  
> have done this in the past in my WOApplication subclasses to be  
> able to report the applicationNumber in log messages when working  
> with WOLongResponse.]