[pylucene-dev] status of pylucene & mod_python

[Ninneman, TJ]

LOL!  Sorry if I "freaked out" on you!

My main reason for moving to Lucene (as is most peoples) from DB based
Full-Text searching was speed, speed, speed.  Of course, my main focus when
coding our Lucene app was raw performance.  If you don't need speed or
concurrency, then by god, do what ever works for you.

TJ


> From: Ofer Nave <ofer at smarter.com>
> Reply-To: <pylucene-dev at osafoundation.org>
> Date: Mon, 26 Mar 2007 08:58:30 -0700
> To: <pylucene-dev at osafoundation.org>
> Subject: RE: [pylucene-dev] status of pylucene & mod_python
> 
>> -----Original Message-----
>> From: pylucene-dev-bounces at osafoundation.org
>> [mailto:pylucene-dev-bounces at osafoundation.org] On Behalf Of
>> Ninneman, TJ
>> Sent: Monday, March 26, 2007 7:24 AM
>> To: pylucene-dev at osafoundation.org
>> Subject: Re: [pylucene-dev] status of pylucene & mod_python
>> 
>> I completely agree.  By doing this you have totally
>> eliminated all the benefits of using mod_python + apache in
>> the first place.  That's why it's best to create web services
>> (XMLRPC, SOAP, etc..) within long running processes.  Then
>> you have total control over the threading model and you'll be
>> able to use other performance tricks such as filter caching.
>> And you'll be able to run any platform on the front end; even
>> lousy Windows/ASP as we do.
>> 
>> Ofer, I would stick to your original plan of using paste to
>> serve up your search content to your front end webserver.
> 
> I appreciate your (and Pete's) concern.  Don't panic!  This is not for the
> production lucene search service.  As of this moment, my intention for that
> is still a small WSGI app plugged into paste httpserver running behind
> lighttpd via SCGI.
> 
> My apache app is purely an internal tools app.
> 
> -ofer
> 
> _______________________________________________
> pylucene-dev mailing list
> pylucene-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/pylucene-dev