On Thursday, July 18, 2002, at 11:47 PM, Fernando Padilla wrote:
Don't waste your time with it. I already know how to get rid of it, it would take about ten minutes..
I would love commiter status. About stopping work on server package, I feel like wittling away at the server code, to make it lean and mean. Then when it's time to surgically remove it, it might be alot easier.
Well, something to keep in mind is that the arcitecture has to maintain a single entity to maintain locks and integrity. A single servlet would do, but then the only way to access it is to send ServletRequests to it...
One slightly different architecture that I might as well propose is to make a local Xindice Class/Interface which would be initialized by a Filter, and would make the Xindice Object available in the Session or in the Request Attributes inside the webapp. Then we could write servlets to deal with the API exposed to the world outside the server. It's an embedded Xindice, but exposed by a specific webapp.
Yeah this is basically what we'll be doing.
shrug, I might not have explained this the best. If anyone asks, I can give a better explanation tommorrow.
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
