Support Requests item #410831, was opened at 2001-03-23 07:32
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=203152&aid=410831&group_id=3152

Category: None
Group: None
Status: Open
Resolution: None
Priority: 9
Submitted By: Adrian Byng-Clarke (adrianbc)
>Assigned to: Kriston Rehberg (kriston)
Summary: Virtual Hosting in AOLServer  3.3.1

Initial Comment:
There have been a recent string of AOLServers that did
not allow virtual hosting out of the box. With the
arrival of 3.3.1 it would seam that the AOLSever 3.x
line is reaching maturity. How does one setup name-
based virtual hosting with AOLServer 3.3.1 ?

 I have 3 (ACS)sites which I would like to run on the
same static IP address. I also want them to all appear
to be running on port 80 so my users don't go mad. How
is this supposed to be done? I have heard of
workarounds such as running local proxies and
installing then debugging modules but I want to know
how this is "supposed" to work in AOLServer 3.3.1 . I
don't neccessarily want all my virtual domains relying
on one process for uptime or performance. Is there any
way around this?

Thank You,

Adrian

----------------------------------------------------------------------

Comment By: Dossy Shiobara (dossy)
Date: 2001-05-30 10:06

Message:
Logged In: YES
user_id=21885

Just a side comment:  No matter how it's implemented, name-
based virtual hosting will ALWAYS rely on one process for
uptime and performance.  Multiple processes cannot bind to
the same IP/port -- only one.  Therefore, whether you have
a single process that handles the socket I/O _and_ serving
content (as Apache does, for instance) OR you have a nsvhr
proxy that handles the socket I/O and then independent nsd
processes that are responsible for serving content, it's
all the same.

What's disappointing is that people don't see the value in
the nsvhr/nsd architecture.  Load balancing becomes much
easier when you have a transparent proxy as part of the
virtual hosting architecture -- I can run my actual nsd's
that are responsible for churning lots of data to generate
my dynamic pages on really beefy hardware, and have the
rest of my non-CPU intensive content (images, static html,
etc.) on pretty puny machines running nsd, and have my
central mux-demux nsd/nsvhr machine grab content from the
appropriate places.  I can scale horizontally in a very
intelligent fashion, where as doing it with a single
heavyweight process like Apache means I'd have to stick a
seperate transparent proxy in front of it in order to
achieve the same effect.

I've been running 9 name-based virtual hosts since
AOLserver 3.0 using nsd/nsvhr with no problems.  It
definitely works.  It may not be as straightforward to set
up as Apache's name-based virtual hosting, but then again,
it's a lot more powerful.  Perhaps a good HOWTO document
could solve this... -- Dossy

----------------------------------------------------------------------

Comment By: Scott Goodwin (scottg)
Date: 2001-05-03 16:01

Message:
Logged In: YES
user_id=37651

AOLserver/OpenNSD 4.x has virtual servers as part of the
core. Haven't take a close look at it or tested it yet.

/s.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-04-10 13:58

Message:
Logged In: NO

Actually my opinion is it isn't a big problem. AOLserver is
not like Apache.
Apache can support virtual hosting without too much impact
on memory requirements, because it can start a new separate
process to handle each connection. For AOLserver to support
single process virtual hosting and keep separate the memory
areas for each server, it has to have more memory, and it
has to have it all the time. Apache closes down an releases
memory. It takes at least one meg of ram per virtual server
in AOLserver 2.3.3. If virtual hosting were put into 3.x, it
would require a similar amount of memory.
With my tclvhr module,  or another proxy you can easily
provide virtual hosting to AOLserver. With tclvhr, the
connection logs are combined, plus there is optional logging
on the individual backend AOLservers.
The vat module should be much easier to setup and maintain
than virtual hosting in Apache., but my vat module goes
overboard even as it is. I wrote it to be extremely general
to not make assumptions about how files should be found and
served. If you had a specific application, it would be easy
to sit down and write a simple virtual hosting module.
My module allows you to add hosts without restarting, and to
configure every aspect of the virtual host on the fly.
Since several other solutions are available, it is hard to
say virtual hosting isn't part of AOLserver right now; it
just isn't officially on the plate for AOL, and never will
be, for the reasons stated above.

----------------------------------------------------------------------

Comment By: Adrian Byng-Clarke (adrianbc)
Date: 2001-04-10 13:23

Message:
Logged In: YES
user_id=180265

Thank you for your post.  I would like to run muliple nsds
on port 80. Will your tclvhr module affect logs?

Also, I realize that there are a couple of ways to get
virtual hosting up but they are not well integrated into
the aolserver distribution as they should be.

This is a **MUST FIX**

 I don't beleive that there is any excuse for having a non-
functional nsvhr around for so many versions of AolServer.
I created this thread to call attention to that fact so
that it can be addressed in the next version.

Adrian

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-04-10 13:04

Message:
Logged In: NO

I have two solutions that have been production for over a
year with not problems.
If your ACS installations are related websites that use the
same database (or different might work too) you can use my
vat (virtual abstract template) module, which uses only one
AOLserver.
If you want separate servers on one ip, you can use my
tclvhr module.
Both are available from http://zmbh.com/discussion/ . Links
at the top of the page.
Read the installation instructions and bug me when you run
into problems.
The tclvhr module, although in tcl is snappy since
AOLserver3.1.

----------------------------------------------------------------------

Comment By: Adrian Byng-Clarke (adrianbc)
Date: 2001-04-10 12:43

Message:
Logged In: YES
user_id=180265

i too am confused. I have been unable to find an adequate
solution to what should be a simple problem.

Adrian

----------------------------------------------------------------------

Comment By: Rob (f1fe)
Date: 2001-04-10 10:12

Message:
Logged In: YES
user_id=193223

I'm confused.  I have AOLServer 3.3.1 (which i downloaded
from aolserver.com), should I be able to do virtual hosting
with nsvhr?  I didn't see the module when i compiled the
source; I followed Jerry's instructions, but haven't had
any success.

Rob

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-03-23 12:45

Message:
Logged In: NO

Check out my AOLserver virtual hosting howto

http://downloads.hollyjerry.org:16080/files/opennsd/virtual-
hosting-howto.html

I've updated it (it's still being worked on) but it
discusses several ways of achieving what you want, with a
brief (mainly to be written) portion on Tom's VAT module,
which I use in conjunction with nsvhr)

Jerry


----------------------------------------------------------------------

Comment By: Adrian Byng-Clarke (adrianbc)
Date: 2001-03-23 09:54

Message:
Logged In: YES
user_id=180265

Can't any of this be done with nsvhr? If not what is its
purpose...

Adrian

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-03-23 09:24

Message:
Logged In: NO

Oops, forgot to put in the url:

http://zmbh.com/discussion/vat/

--Tom Jackson

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-03-23 09:22

Message:
Logged In: NO

My virtual abstract templating module handles virtual
hosting, abstract filenames and global templates grouped
into modules.
Although not the easiest to figure out at first, it handles
virtual hosting very well.

--Tom Jackson ([EMAIL PROTECTED])

----------------------------------------------------------------------

You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=203152&aid=410831&group_id=3152

Reply via email to