On Mar 27, 2010, at 1:08 PM, Russell Keith-Magee wrote: > Option 3: We modify the existing signals so we have a pre-post pair > for every signal. This maintains the analog with pre/post save, and > gives the most control. For example, on Alex Gaynor has suggested to > me that some people might want to use a pre-add signal rather than a > post-add signal for cache invalidation since there is a marginally > lower chance of getting a race condition. However, signals aren't free > -- an unattached signal is roughly equivalent to the overhead of a > function call.
I'm +1 for this. But, I'm also the person who proposed it on the ticket. :) I've had uses for pre- and post- on at least changed, and worked around the add/remove being on one side or the other. I'd happily eat the extra function call worth of overhead for the general case. George -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
