belred wrote: > i'm having touble finding documention about django signals that > explain how they behave under apache child processes. if i have a > signal go off and have a listener for that signal. will only the > listener in same child process receive it or will that same listener > in all apache child processes receive it? > > what is the best way to signal all of your apache child process for > you project? I don't think the intention of Django signals is to allow notifications to be sent to independent processes. It's more that when a request causes certain things to happen then signals can be used to notify an appropriate handler that it's time to run. In other words it's a flexible communications mechanism for in-process (single-request) decoupled notifications.
What events are you feeling the need to notify to all your Apache sub-processes? Maybe there's some more appropriate mechanism you could use ... or I could be wrong about Django signals. regards Steve --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
