But I think that some configuration along these lines would be extremely simple to implement and provide the Xindice administrator complete control over what XMLRPC methods are exposed and even allow him/her to add his/her own methods without mucking inside the core of Xindice.
Gianugo things it's not a good idea. You think it's a good idea.
Who's right?
If this configuration sounds good, I'll make the changes ASAP since I really would like to see a configurable xmlrpc server in 1.1. I don't know where the configuration information should live, so if people think this config is ok, I'd like to hear where they think it should live. Perhaps alongside system.xml, there should be a drivers.xml or a xmlrpc.xml?
Ok so now every "driver" (or client) potentially needs its own configuration file. Moreover, some configuration file are only meant to be on the server (xmlrpc.xml) and/or on the client (system.xml for the embed driver). We don't have to forget the security configuration file which will be either on the server (xmlrpc) and on the client (embed mode, but NOT xmlrpc mode).
Did I heared someone talking about a "centralized" configuration?
-Vladimir
-- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
