> Then the RPCMessageInterface class would parse this config file on startup. > When a request comes in, it would invoke the run method as it does > currently.
Ok I'm going to be once again umpopular... [Q] Do we really need this? [A] Not now and maybe not at all. For several reasons: - this solution is more complicated than simply referencing a method by its full path - this solution requires the user to edit some config files (copy/paste errors). - this solution requires the user to take care of the uniqueness of the keys - ... I don't say that this is not an interesting solution, I just say that you don't know if it really solves the problem. The best way to find out would be to first implement other XML-RPC messages (like the Grep) and then come with a solution that solves real problems (and not the ones you think you will maybe have in a distant future). I don't want to have the Xindice 1.0+ situation when some features were only half-implemented. Like the xindice tool that required a configuration file when accessing a local db but didn't do anything with that file. This is the best example of a good idea (define a configuration file: OK) but a bad implementation (not reading it: NOT OK). The same thing with the filer: you can still specify a filer in the configuration file but it's never taken into account. My motto: do not build a Boeing 777 if you may only need a Cesna -Vladimir ===== Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
