My comment on part 1.
With orion you don't need apache or any other webserver. Orion handles
all that very well.
It is possible though to use apache as plugin or is it the other way
around...?
My comment on part 2.
Go ahead and mix the files all you want or in a way you are comfortable
with. One thing with mixing static and dynamic pages that really bugs me, is
that when you change your mind about some static content and want it dynamic
you rename it to .jsp and change a couple of billion links. Why not call
them all .jsp and some of them can look just like a html file except the
file ending. Theyre compiled anyways so it should be fast enough...
regards
Johan Fredriksson
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 7:40 PM
Subject: Orion web server vs. apache or IIS
> Hi:
>
> I just got Orion and noticed that it is recommended that we use the Orion
> webserver as apposed to plugging it into Apache for instance. I was just
> wondering what, if any functionality that the Orion web server may lack
> versus the others previously mentioned?
>
> I am coming into Orion and J2ee from an IIS Asp background and am little
> unclear as to the separation of the web app container vs. the webserver?
In
> IIS I did not see such a separation, so when you created an
> application/dynamic web site, you put all the files (dynamic or otherwise)
> in the same directory root. With Orion, is this the same or does the
static
> web content have to be separate from the dynamic stuff?
>
> Thanks,
>
> Stefan
>
>
>
