> I feel like the addition of Terry's work is not an add-on, but more of a core > functionality. WebDav on the other hand could be an add-on as it is a db > access method vs. db filer/indexer code, so I'm not against such a library.
Terry's work is certainly very useful (he uses it) but it targets a specific usage of Xindice (loading the entire db in memory is not done by every user). By "addons" I distinguish between default/non-default functionalities and not between core/non-core functionalities. Of course a feature can be moved from the addons to the main trunk. A good example is the BerkeleyDB filer: it's a core functionality (filer) but clearly an addon (requiring external resources). One of the advantages of an addon project is a much shorter release cycle. (JUnit-addons has a new release every month, JUnit every year). But I don't say that everything has to go into the addons. The scheduler (if you can tell a little bit more about it) should certainly be a default feature. I hope that I made things a little bit clearer. -Vladimir -- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
