Ok, sorry.

My thought train is limited to the IIS vocabulary and concepts, forgive me.

- Tormod

-----Original Message-----
From: Jeff Ramin [mailto:[EMAIL PROTECTED]]
Sent: 30. august 2001 15:19
To: JRun-Talk
Subject: Re: use-webserver-root, default application and static web app
content revisited...


Tormod Hystad wrote:
>
> No, Jeff, that will not help at all. One sinle Apache instance still has
> only one web server document root,

Not true.  A single Apache instance can have N document roots.  I'm
running it in that configuration with JRun on my laptop.

Read the doc, or ask for help.


> so I'll still need one Apache instance
> pr. "optimized" JRun Web Application/Jrun Server (optimized by setting
> <web-app-name>.use-webserver-root=true)
>
> Apache is ok, but it is not the "Endlosung" you diciples want it to be for
> every problem....
>
> Any other thoughts anyone?
>
> ~ Tormod
>
> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> Tormod Hystad
> Senior Developer, R&D
> CatalystOne, Inc. - Execution excellence!
>
> <Snip>
> > 2. The other option is to "mark" the application as a default web
> > application, in contrary to the additional web application from the
> example
> > above (these two terms are defined in devapp.pdf page 72 from the JRun
3.1
> > docs), by setting the <web-app-name>.use-webserver-root=true parameter
in
> > local.properties of the server (and/or webapp.properties for the actual
> web
> > application?). This will cause the JRun connector to skip the JRun
> roundtrip
> > for static content, and lett IIS serve this content. Scott Stilring
stated
> > that this was much faster than option 1.
> >
> > This approach has one major limitation:
> > - Only one can exist per "site" in IIS, since you define web server
> document
> > root pr "site" in IIS. This means only one can exist per server in JRun,
> > since each JRun Server needs a separate IIS site. This is not good for
> > development/testing purposes at least. Cost conscientious production use
> > neither.
> </Snip>
>
> <Snip>
> Use Apache!  That may not be an option for you, but Apache handles
> this situation with ease.  You can have a single Apache instance talking
> to as many JRun servers as you want.
> </Snip>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to