Vladimir, sorry I didn't realize we were not posting to the list. I want to keep these conversations public if you don't mind.
Clearly a need (#3) has been presented by Terry for this filer. This need now exposes another need to expand Xindice to handle it (#2). Maybe since we accepted this contribution, Terry will be inclined to get back on the main trunk and he may contribute a configurability patch. If we never listen to what one of our dedicated users needs, how is this a community? Doesn't that make sense? Your thoughts below are based on the predisposed notion that we know how everyone will use Xindice. Terry has proven that theory wrong. We cannot control how people use the project, just help organize everyone. This is not a perfect world. There is not perfect order. We just roll with the punches and keep moving. XP development methodology speaks to this subject in particular. What do you think? -Kevin -----Original Message----- From: Vladimir R. Bossicard [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2003 2:14 PM To: Kevin Ross Subject: RE: [offline] Re: [my philosophy] was RE: MemValueIndexer > You might be able to configure these for each collection...why wouldn't > that be possible? I don't ask you if you "might". I ask you "how" you do it. AFAIK (but I may be wrong) you can't. Xindice is not configurable to the point of letting you define the filers you're using unless you write your own Java client. What's the point of having different filers if you can't use them? The normal process should be: 1) create several filers (done) 2) make Xindice accepting those different filers (not done) 3) develop other filers (done) what's the advantage of having 1) and 3) if you don't have 2) ? If you don't see that, it's true we can't understand eachother. -Vladimir -- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
