> If we make the Xindice addons truly modular, then any of the proposed > metadata solutions as well as other non-essential features can be > easily added to a Xindice application without enlarging the core code > and complicating the lives of those who don't want or need metadata. > I like the idea of a trim Xindice rather than including everything, > and given this is a public process I'd hate to see it bloat out like > some things.
How can we do this in a similar fashion to 1.0? The configuration file in 1.0 allowed us to add and remove components in a very nice way. Using the config file wasn't really documented, and I'm sure there are some components that most people don't even know about (HTTP GET handler for document retreival, the XML-RPC server, and a DB Conduit for connecting to JDBC datasources from Xindice, etc.). Kurt
