Although bongoyo is functional right now, there are lots of areas in which it can be improved, perhaps even need to be improved. Here is a partial list of the wishes:
Currently the approach is really ad hoc. A more systematic approach needs to be implemented, and should include run-time minor adjustments, and dynamic reconfiguration on the fly. Probably a good approach is to read everything into an organized list first before acting on it, rather than acting on each line immediately upon reading.
There is currently no way of querying bongoyo to obtain the status of the system except for the log file. A method/module should be devised to allow this.
Should allow for limited control of stuffs, like forcing a fail-over server to give up a virtual server, or force boss selection, etc.
A good idea to have a web interface for status viewing and run-time control.
The current authentication method is of the brown paper bag variety.
Needs to have flexible/automatic determination of time outs. Currently the time outs are hard coded into the main program. Need to move them out to the configuration file.
I had thought that the Syslog perl module is not part of the standard install, so bongoyo logs (badly) to a file. Need to correct this.
Like all programs, bongoyo needs to be really combed through for bugs that I can assure you will find a-plenty.
Page mangling by Edwin Lim.
Mon Sep 11 00:59:57 EDT 2000