If it's for a service that just runs all the time once it's set up, fastcgi+lighttpd is not bad at all. Setting it up is an one time effort.
If you want a more portable solution, just like using an embed-able server jetty in solr, you can use a more efficient async Python web server (e.g. the one in cherrypy) and call PyLucene right from inside your own server. Not sure how much load it can handle but the bottleneck should be in PyLucene, and because it's one Python process, it won't run on multiple processors. If you want to use more processors, lighttpd + multiple Python fastcgi servers would be the way to go. -- Best regards, Jack Tuesday, March 20, 2007, 10:12:22 AM, you wrote: > You know, I've never really considered FastCGI for anything before, but that > doesn't sound like a bad idea. Still not as simple as deploy and run, since > there are still two pieces (FastCGI/PyLucene and lighttpd), but possibly > simpler (and possibly faster) than apache. > -ofer __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
