Hi Till,
Unless you use the fair-loadbalancer-module in nginx -- and even that one has a couple minor issues -- nginx based load balancing is no better than DNS.
The difference is that a "real" loadbalancer like pound or haxproxy would route a request to the backend that has the least load and also provide what is called "stickyness" (which is basically what your patch does) and at the same time providing the failover in case the backend is overloaded or becomes unavailable.
I knew apache could proxy with "sticky session", I did not notice
Pound had that feature, so I will have recall my previous mail :D
It would seems that my path of least resistance is to simply replace
nginx by pound for http/https proxying and just keep it for imap/pop
load dispatching.
I hate to be shown wrong :D
http://trac.roundcube.net/wiki/Plugin_Hooks
The bottom line is to use the plugin hooks. E.g. use login_after to set your cookie. If you happen to need another hook, just let us know, and we'll roll it in. :-)
Thank you for the time you took to answer my email and clarify your
statements.
Should a configuration of pound for such deployment be added to the
wiki ?
(coming back to the point made about Daniel about helping roundcube
users with their deployment).
Regards,
Thomas _______________________________________________ List info: http://lists.roundcube.net/dev/