lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <>
Subject Re: Proposal for Lucene / new component
Date Tue, 26 Feb 2002 13:12:38 GMT
On Tue, 2002-02-26 at 05:35, Kelvin Tan wrote:
> Pls see inline reply.
> ----- Original Message -----
> From: "Manfred Schäfer" <>
> To: "Lucene Developers List" <>
> Sent: Tuesday, February 26, 2002 7:23 PM
> Subject: Re: Proposal for Lucene / new component
> > Hi,
> >
> > "Andrew C. Oliver" wrote:
> >
> > >
> > > I'm trying to learn enough about avalon to do this.  I'm having a hard
> > > time of it.  After I read the conceptual documentation and see a couple
> > > of code samples I'm like "now what?"  I need a "hello avalon" tutorial
> > > to help me.. . U/f I can't write one (chicken and the egg kind of
> > > thing).  I still am having trouble figuring out how to do something like
> > > this via ant or even if ant is the right tool..  (I mean I love it for
> > > builds but for this??) MAybe I have a mind block :-)
> >
> > Ok. I have a few deficienies in my personality: I'm reading texts of other
> people mostly superficial, writing mails to forums, bevor i'm really
> completed with thinking and some more, which i will tell you later.
> > Ant could be used for writing configurable indexing engines, but that
> smells little bit like misuse of ant, you're right for that.
> > I've also had a look at avalon last week: To me it seems like the
> standardization of the meta pattern [interfaces, factories, proxies, managed
> objects, etc..]. Exactly the same kind of coding, which shines through
> kelvins code. So avalon itself is merely a collection of interfaces,
> Abstractfactories etc. It is surely a starting
> > point for architectural considerations, but doesn't deliver anything more
> (kind of academical).
> >
> Personally, I'm not altogether comfortable with Aspect-Oriented Programming
> (though I've been told I'd better, because it's the "future of
> programming"). I guess it just doesn't seem quite as intuitive and natural
> as OOP. And Avalon has a pretty huge emphasis on AOP. In fact, one might say
> it is the programmatic manifestation of an AOP-based component framework
> (based on my limited understanding of it).
> I guess adopting Avalon is more of a way-of-life (or style of coding) than
> it is a mere design decision, and I guess it's not something that I'm
> totally prepared for yet. Maybe its because I haven't designed sufficiently
> large/complex systems to appreciate the benefits it (and AOP) provides...:-)

Humm.  Well said.  I'm not against using Avalon.  My approach to
software is this though:  Get a working draft.  Refactor it into that
*stand the test of time* for your second or third release.  Things
change...iterate.  Not against a super configurable masterpiece...but
first I want to crawl and index web pages over httpd in various
pluggable mime formats.. Once we get there...

> Regards,
> Kelvin
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>
-- - port of Excel/Word/OLE 2 Compound Document 
                            format to java 
			- fix java generics!
The avalanche has already started. It is too late for the pebbles to
-Ambassador Kosh

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message