Stefan de Konink wrote, On 21/12/06 22:08: >> No, it doesn't need any sort of DNS tweaking. The client >> requests go through Cherokee to a destination server (that >> usually are placed in the intranet), and the outgoing replies >> goes through Cherokee as well. All the traffic seems to be >> generated by the public Cherokee server, even if it is actually >> generated by server in the intranet. > > If the mirror server is down. Everything is down. It would be nice > if it was possible to have some round-robin system in there. That > actually takes over if one of the mirrors fail...
The balancer mechanism is flexible, so it's up to us to implement as many balancer plug-ins as we want. Currently there is only one in trunk branch, but I'm looking for interesting ideas on how to improve it and what could be interesting for writing more modules. >> > So in a simple way: is it possible to have some 'callback' feature >> > or status interface so it is possible to link it to a third party >> > management tool? >> >> I'm not sure about what you asking. >> >> Cherokee includes a remote administration handler called "admin", >> maybe that's what you are looking for. > > I'm was thinking about something like 'if the handler fails then execute > command'. It's a good idea, indeed. :-) -- Greetings, alo. http://www.alobbs.com _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
