I just did some tests with a very simple servlet to start Xindice and I found that Tomcat was significantly faster then the built in webserver. The XML:DB API tests run in roughly 18-22 seconds on the old framework and 13-15 seconds under Tomcat. Given this, I'm really itching to finally pull the trigger on all the code in the server package. We'd end up replacing about 60 classes with just one or two and get better performance to boot. I also see significant architectural advantages to this as mentioned in a previous mail.
The main downside is that things like the CORBA API hang off the old server framework and wouldn't be able to work anymore. For that I'm thinking I could just package a shell of the old server which you could just drop a xindice.jar into and have it work with the latest code. At some point it will break, but maybe someone will be motivated enough to pick it up and maintain it as a separate project.
I need to hear other opinions on this. In particular why we shouldn't do this?
Kimbro Staken Java and XML Software, Consulting and Writing http://www.xmldatabases.org/ Apache Xindice native XML database http://xml.apache.org/xindice XML:DB Initiative http://www.xmldb.org
