[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: How?



Igor Mendelev writes:
>1. Why recommended port configuration is 80 for TUX and clientport is 8080
>for Apache (or whatever) - and reverse is described as less useful? 

Because most people want their web server on port 80...

TUX responds to requests much faster than apache, so having TUX
respond to all pages it can directly on port 80 and having apache
back up on port 8080 (accessed locally; from the remote side it
is still port 80...) make more sense.

>2. Did anyone actually tested running Resin or other servlet/JSP engine
>together with
>TUX (on the same box but different ports)?

Not me!

>3. threads parameter - should it be 1 or 2 on 2 CPU box; what should it be
>on 4CPU box
>- assuming only TUX is running

Normally 4 (the default).

>- assuming JSP/servlet engine is running also on different port?

That would require tuning.

>4. Does it (or will it) support SSL?

Only by forwarding to user space.  Most of TUX's benefits are not
carried over into SSL -- for example, you can't cache tcp checksums
for outgoing SSL data!

michaelkjohnson

 "He that composes himself is wiser than he that composes a book."
 Linux Application Development                     -- Ben Franklin
 http://people.redhat.com/johnsonm/lad/





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []