look to the site www.orionserversupport.com there are many useful articles and tips, including one on how to use Apache as a "proxy" to orionserver ie.e. apache serves the static html, while orion serves servlets/jsp and manages ejb invocations.. > -----Messaggio originale----- > Da: Lucio Piccoli [mailto:[EMAIL PROTECTED]] > Inviato: mercoledì 12 settembre 2001 11.13 > A: Orion-Interest > Oggetto: webserver proxy plugin + i/o question > > > hi all, > i am new to orionserver but i have read the docs and the > archives relating > trying to find information relating to: > i) Webserver proxy plugins > ii) The type of i/o handling used. > > A variety of appserver vendors (BEA/IBM) recommend an > architecture of a high > performance webserver ( iplanet/apache ) proxying on requests to the > appserver. This has several benefits including limiting the > exposure of the > appserver to the outside world. I was hoping to eval orionserver in a > similar environment. However the only mention of a webserver > handling in > orion is to use the tunnelling servlet which still seems to > require the > orionserver to be exposed to the outside world. Is this the case? > > What is the I/O mechanism used in orionserver's request > handling? I assume > that it is using java's blocking i/o, is this correct? > > any help appreciated. > > adios > > -lp > -------------------------------------------------------------------- > [EMAIL PROTECTED] > Titan Court > 3 Bishops Square Business Park > Hatfield AL10 9NE > Hertfordshire England > tel : +44 01707 289 798 > fax : +44 01707 289 941 > __________ http://www.one2one.co.uk _____________ > > > > > NOTICE AND DISCLAIMER: > This email (including attachments) is confidential. If you > have received > this email in error please notify the sender immediately and > delete this > email from your system without copying or disseminating it or > placing any > reliance upon its contents. We cannot accept liability for > any breaches of > confidence arising through use of email. Any opinions > expressed in this > email (including attachments) are those of the author and do > not necessarily > reflect our opinions. We will not accept responsibility for > any commitments > made by our employees outside the scope of our business. We > do not warrant > the accuracy or completeness of such information. > > >
