Re: lucene API

2005-08-18 Thread Erik Hatcher
On Aug 18, 2005, at 1:09 PM, Maros Ivanco wrote: To: [email protected] From: Erik Hatcher <[EMAIL PROTECTED]> Date: 18.08.2005 3:45 Subject: Re: lucene API When I first started digging into the Lucene codebase, I felt similarly - the coding convention rule breaking drove m

Re: lucene API

2005-08-18 Thread Maros Ivanco
-Erik Hatcher <[EMAIL PROTECTED]> wrote: - >To: [email protected] >From: Erik Hatcher <[EMAIL PROTECTED]> >Date: 18.08.2005 3:45 >Subject: Re: lucene API > >When I first started digging into the Lucene codebase, I felt >similarly - the coding

RE: lucene API

2005-08-18 Thread Robert Engels
ce APIs use a far simpler "consumer" interface. Robert Engels -Original Message- From: Maros Ivanco [mailto:[EMAIL PROTECTED] Sent: Thursday, August 18, 2005 11:40 AM To: [email protected] Subject: RE: lucene API -"Robert Engels" <[EMAIL PROTECTED]>

Re: lucene API

2005-08-18 Thread Maros Ivanco
factories following desing patters, extract interfaces and so on. Maros. -Daniel Naber <[EMAIL PROTECTED]> wrote: - >To: [email protected] >From: Daniel Naber <[EMAIL PROTECTED]> >Date: 17.08.2005 20:32 >Subject: Re: lucene API > >On Wednesday 17 August

RE: lucene API

2005-08-18 Thread Maros Ivanco
-"Robert Engels" <[EMAIL PROTECTED]> wrote: - >To: >From: "Robert Engels" <[EMAIL PROTECTED]> >Date: 17.08.2005 16:20 >Subject: RE: lucene API > >I think you should leave the API as is, and write a custom XML writer >for >luc

Re: lucene API

2005-08-17 Thread Erik Hatcher
When I first started digging into the Lucene codebase, I felt similarly - the coding convention rule breaking drove me nuts. Lucene grew on me and I've changed my take on "conventions" dramatically thanks to Doug's explanations and the flavor he has imparted onto the codebase. His "conven

Re: lucene API

2005-08-17 Thread Daniel Naber
On Wednesday 17 August 2005 15:26, Maros Ivanco wrote: > I would personally prefer the third one, but only if the changes will > make it to the official release. Whether a patch is accepted can obviously only be decided when we see the patch, so no promises can be made. Regards Daniel -- htt

RE: lucene API

2005-08-17 Thread Robert Engels
I think you should leave the API as is, and write a custom XML writer for lucene search results. The request is trivial since you can simple pass the single string. I would not write wrapper beans just to use the built-in serialization support. The custom XML writer will be MUCH, MUCH faster, as y