[EMAIL PROTECTED] napisaĆ(a): > It would be very helpful to know if the Django Dev. team has any plans > to include support for > Pylucene/ Django.contrib.search feature in the near future?
PyLucene poses very specific problems. Basically, there are 2 flavors, GCJ-based PyLucene and newer JCC-based. Of these two, the GCJ-based PyLucene is much stable and faster, but has a flaw that prevents it from using in *any* web-based application -- it does not allow the process where it is used to be forked *at all* and seriously limits the possibility of threading (basically, you can only have one thread with GCJ-based PyLucene). This means, you'd better try to write separate search/indexing server (i.e. based on Twisted) than fight the fight you'd never win. The JCC-based build is very new and although seems to be stable enough to be used for development, it is not as extensively tested as GCJ-based. It has some interesting concepts when it comes to threading but I did not find any information on how it works with forked processes. -- Jarek Zgoda Skype: jzgoda | GTalk: [EMAIL PROTECTED] | voice: +48228430101 "We read Knuth so you don't have to." (Tim Peters) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---