[Bese-devel] single-threaded

[Attila Lendvai]

> So, is it ok if I revive the single-threaded httpd, or make a
> single-threaded iolib based backend? Or do you have any plans that
> conflict with this?


i'm planning another controversial change, namely completly depending
on iolib and using usocket only for the httpd backend. the moves you
see is mostly guided by making ucw a web server that can cope with
high load as a public site (iolib, threads, etc).

this does not mean that single threaded mode is not welcome of course,
but for now i've merged the httpd backends for simplicity/cleaning up.
i'm also planning to keep httpd in a fallback-for-mostly-debugging
status and concentrate on a flawless DOS-proof iolib backend capable
of handling thousands of connections.


> Is anyone interested in example files for configuring haProxy, nginx,
> apache and pound? I have been through them all by now. I can't say
> firmly which one is best, but I see it like this:


i'm also planning to add an iolib based load-balancer, because
mod_proxy_balancer in apache is mixing up connections sometimes,
returning entire responses to different clients (with a working
session id!)


> apache. Well tested, lots of features.


well, tested... :)


sorry for the short answer, expect more later

-- 
 attila