Hi Sam,

I am the author of TurboLucene. :)  All the source is in the
__init__.py.

TL is still pretty young and evolving (albeit more slowly than I would
like.)  I do plan on breaking the out of __init__.py into separate
modules.  I also plan on providing some kind of full PyLucene access
at some point.  (I just personally do not need it.)

The way I dealt with the threading issues is to have the main Python
loop create an indexer thread and a searcher factory thread (as
PythonThreads).  Then the API just sends messages through some
Queues.  It's convoluted, but I think it is better than trying to
monkey patch CherryPy.

Anyway, hope this helps.  Why not join the TurboLucene mailing list?
That's probably the best place for TL-related questions, and I'd
certainly love to hear any thoughts/suggestions you have about TL use
and PyLucene use in general.

Thanks,
Krys

On May 28, 11:54 pm, SamDonaldson <[EMAIL PROTECTED]> wrote:
> Guys,
>
> I downloaded the turbolucene source code, but I just don't see any of
> the files that have to do with the source?  How does Turblucene
> connect to pylucene?  Where's the code that takes care of the
> threadying issue in CherryPy?  I would love to be able to connect to
> pylucene directly without using another layer of API's provided by
> Turbolucene.  Can somebody help here?
>
> Thanks.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to