Dnia czwartek, 15 września 2011 o 18:14:39 Roberto De Ioris napisał(a): > > I'm thinking about setup like this: > Well, the best approach seems to have a subscription server that send its > data (domain names and backends) to varnish via its admin protocol. > > Varnish will continue to directly connect to uWSGI instances (in native > http mode) but its configuration will be constantly upgraded/adapted by > this additional (and very cheap) process. > > At low level it will became something like this: > > uWSGI node1 subscribe to subscription server > uWSGI node2 subscribe to subscription server > > subscription server constabtly check if something is changed and > eventually generate a new director stanza for varnish and will update it > via its internal admin protocol. > > Someone interested in this kind of plugin ? Maybe we could follow a more > generic approach and execute custom code in a dumb subscription server:
More features is always nice to have, especially if it allows to have simpler setup, so I would be very happy with such approach. I think that possibility to write fastrouter handlers would be a better solution, as it would allow others to plug uwsgi into other load balancing/reverse proxy setups and/or add some custom features. Łukasz Mierzwa _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
