> -----Original Message----- > From: Vladimir R. Bossicard [mailto:[EMAIL PROTECTED] > Sent: 11 December 2002 14:43 > To: [EMAIL PROTECTED] > Subject: Re: [2.0] slowly moving towards Avalon > > > > > I feel Avalon is overkill for what we need: configuration > of components is only a minor issue in Xindice, and the > current framework works fine IMHO... > > I forgot 'e.g.' when talking about configuration. From what > I've seen, > the configuration doesn't currently handle more complicated > configurations (multiple children with the same name). > > Of course you can always spend some time enhancing the > Xindice class but > I prefer to use what's already out there. > > And the configuration is only an example. I have no experience with > Avalon but I think that it can bring more than just the configuration. >
That's true. However, from the contact I've had with Avalon using Cocoon it is s *HUGE* and quite complex framework, and frankly Xindice is too simple to benefit from it. All Xindice needs is to start up a server engine, create accessors to it, and that's it. Starting up the engine involves configuring the root collection, getting the system data from it, and settings up filers and XML manipulation classes. That really isn't all that complex from the Avalon point of view. I maintain my belief that effort should go into real database work: optimizing storage, getting queries to execute efficiently, transactioning and failover etc... the current Xindice framework fully allows working on such items. It is precicely for such work that I started the "internals" guide as it should provide some starting points for developers to start looking at these areas. James
