On Fri, Nov 6, 2009 at 3:14 AM, Alexey Pechnikov <pechni...@mobigroup.ru> wrote: > Hello! > > On Monday 02 November 2009 04:14:17 Tom Jackson wrote: >> On Fri, Oct 30, 2009 at 9:36 PM, Bas Scheffers <b...@scheffers.net> wrote: >> > I do this for a couple of sites, Apache's mod_proxy forwards stuff to >> > AOLserver. This is mostly where we have a scarcity of IPs. >> > >> > But that still means you have to jump through hoops to install it, learn >> > how >> > to run it in production, etc. >> > >> >> It is strange that the most valid reason to use Apache is a lack of IP >> addresses. But it's true. > > Why Apache? I'm using AOL Server cluster with single entry-point > managed by HAProxy. I did use Pound some times ago.
This only applies if you must use Apache. Apache is obviously more flexible than AOLserver in this area, but any proxy server would do. The one area where Apache seems to beat AOLserver from a design standpoint is serving many unrelated virtual hosts. AOLserver must load each virtual host into memory even if you use the CGI module. Of course, if the virtual hosts are all managed by the same admins, you can do soft virtual hosting inside of a single AOLserver instance. But, you can't allow 2+ admins under a single AOLserver instance...unless you don't allow the admins to use untrusted code which can access the AOLserver or Tcl API. For example, my <tic-tac-toe> template system would allow admins to provide their own templates without introducing security issues. - Show quoted text - >> >> > I'd love a being able to just say "apt-get install apache2-aolserver >> > apache2-aolserver-postgresql". >> >> As soon as apt-get blah-blah-blah starts installing software where I >> want it, with the options I want, I also would love it. But if I >> install an AOLserver for a client, they might want to keep their >> version for a few years, the next client might want the current >> version and a new postgresql. The apt-get stuff works exactly once per >> machine and it still doesn't give much flexibility. Eventually you >> have to learn how to do custom installs. > > For AOL Server there are not additional packages now but it's not the > problem of AOL Server. We can build a set of packages. As example > aolserver4-openacs-framework > aolserver4-mbg-framework > ... > > And we can have different AOL Server builds: > > $ apt-cache policy aolserver4 > aolserver4: > Installed: 4.5.1-mobigroup.5 > Candidate: 4.5.1-mobigroup.5 > Version table: > *** 4.5.1-mobigroup.5 0 > 500 http://mobigroup.ru lenny/main Packages > 100 /var/lib/dpkg/status > 4.5.0-16.1 0 > 500 http://mirror.yandex.ru lenny/main Packages > > The 4.5.1-mobigroup.5 is my own build with tcl 8.5 and some bugfixes. Is not > difficult to add other builds. I'm not sure who does the adding? The problem is when you want to maintain two independent AOLservers on one machine. That is two independent Tcl installations, two of everything. The apt bs works if you use apt, what if you don't want to, or can't? You just substitute understanding how to build AOLserver with the need to understand apt. Neither one is particularly more or less complicated if you have to do anything special. >> I like the idea of a forward (caching) proxy, it fits in well with the >> filter type architecture in AOLserver. > > I don't understand which tasks it can resolving? Caching of expensive content: dynamic content which is used many times before it actually changes, like the front page of a news site. Even the time of day only changes once per second, if you get a 100 hits per second, caching cuts your backend load by 99%. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
