Kelvin, Have you had a chance to check in any of your search subsystem components? I know it's been a while since I mentioned the issue, but I'd love to make some headway on a solid Turbine search subsystem for general consumption.
Thanks, Seth -----Original Message----- From: Kelvin Tan [mailto:[EMAIL PROTECTED] Sent: Sunday, January 26, 2003 8:17 PM To: Lucene Users List Subject: RE: Lucene Turbine Service Seth, I had been meaning to do it for awhile, but inertia was overwhelming. Then I recently needed to be able to modify the configuration of the service at runtime, and Fulcrum didn't support that, so I just refactored my way out of it. :-) Why had I been wanting to do it? well, on hindsight, I think it never was a good candidate for a turbine service in the first place. the way i see it, a good candidate requires a) Lifecycle support b) Configuration c) Pluggable implementations For LuceneSearchService, a) was minimal, b) yes but not a big factor and c) turned out to be impractical. I had hopes of creating a SearchService where one could plug-in various implementations (check out http://www.mail-archive.com/[EMAIL PROTECTED]/msg01461.htm l) but gave up in the end. Let me see if I can cleanup the subsystem I've refactored out and check it in to Sandbox, then maybe we can discuss from there? KT On Tue, 21 Jan 2003 19:35:40 -0500, Seth Weiner said: >Thanks for the pointer! Might I ask what the motivation for the >refactoring was? > >On a separate note I just took a look at the service in the sandbox. It >doesn't appear to support addition of documents to the index. Shouldn't >be hard to add, just seems like a strange ommision. Also, wouldn't it >be more efficient for the service to maintain a pool of IndexSearchers >rather than creating a new one for each search? Or is there a problem >with holding one or more index searchers open on an index? To >add/remove a document to the index, would all of the IndexSearchers >need to be closed, or is this safe to do? > >The simple app I'm trying to write allows for the searching of an index >through a turbine webapp interface as well as the ability to upload a >document through the webapp to be added to the index. If the document >exists in the index it's deleted and then the new version is added. >If anyone's already done this feel free to share;) And while you're >in a charitable mood, my next step is to take the Lucene service and >make it an XMLRPC webservice. Thoughts and suggestions on that idea >are greatly appreciated. > >Thanks, Seth > >-----Original Message----- >From: Kelvin Tan [mailto:[EMAIL PROTECTED] Sent: Tuesday, >January 21, 2003 7:16 PM To: Lucene Users List Subject: Re: Lucene >Turbine Service > > >Yep. Look in Lucene Sandbox. Interesting you should ask, though, >because after about a year of using the LuceneSearchService, I've >recently refactored it out into a subsystem of its own...:-) > > >Regards, Kelvin > >-------- >The book giving manifesto - http://how.to/sharethisbook > > >On Tue, 21 Jan 2003 18:44:33 -0500, Seth Weiner said: >>Hi, >> >>I'm fairly new to Lucene and am trying to create a 'simple' Turbine >>webapp that will use Lucene for some indexing. Has anyone written a >>simple Turbine/Fulcrum Lucene service for searching and indexing >>documents? >> >>Thanks, Seth Weiner >> >> >>-- >>To unsubscribe, e-mail: <mailto:lucene-user- >>[EMAIL PROTECTED]> For additional commands, e-mail: >><mailto:lucene-user- >>[EMAIL PROTECTED]> > > > > >-- >To unsubscribe, e-mail: <mailto:lucene-user- >[EMAIL PROTECTED]> For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > > > >-- >To unsubscribe, e-mail: <mailto:lucene-user- >[EMAIL PROTECTED]> For additional commands, e-mail: ><mailto:lucene-user- >[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
