On Fri, May 8, 2009 at 9:48 AM, Thomas Mangin <[email protected]> wrote: > Hi Till, > > Thank you for taking the time to read my mail. > (...) >> Besides you should >> probably use a "real" load balancer (like HAProxy or Pound, or maybe >> even hardware) to spread out. > > HAProxy or Pound (or even Varnish [1]) are no more "real load balancer" than > NGINX. > And I see no need to invest in an "hardware solution" (ie: which is just a > nice way to say an expensive hardware + software bundle) when I have > everything I need in the OSS landscape.
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. > (...) >> Round-robin doesn't safe guard against that, but e.g. a load balancer >> would. > > I assume you meant "e.g. load balancer with roundcube using a shared DB > would" :) Yeah, a loadbalancer and a shared database. > I was not focusing on high availability - like the need of DB replication, > etc. Did I mention it? >> But anyway, did you progress with the plugin api? > > I explained why I thought it was not possible. Do you think I am mistaken ? 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. :-) Till _______________________________________________ List info: http://lists.roundcube.net/dev/
