I'm not sure how you're deploying, but most people use multiple processes rather than a single process. Given that, an in-process mutex will do you no good.
If you really are single-process, Django does not have a built-in mutex, but maybe you want: http://docs.python.org/lib/module-mutex.html On 8/17/07, Derek Anderson <[EMAIL PROTECTED]> wrote: > > no, not trying to farm out many threads. already have many threads > running. (from apache) and (obviously) there is no master thread to do > the coordination. see: http://en.wikipedia.org/wiki/Mutual_exclusion > just want to make sure no two threads are entering the same critical > section at the same time. > > > Jeremy Dunck wrote: > > I think you want gearmand: > > http://www.danga.com/gearman/ > > > > It has a 'uniq' property that ensures only one job with a given name is > > running. > > > > On 8/17/07, Derek Anderson <[EMAIL PROTECTED]> wrote: > >> i have a number of background threads in my app, and for a few of them i > >> want to make sure only one of them exist. (not one per server thread) > >> > >> for instance, my bigram indexer....or my notification mailer. > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
