On Mon, 2006-10-23 at 17:38 +0200, Michael Radziej wrote: > Hi, > > I grew myself a way to output warnings in a similar way as > validations work, and I also use this to check domain names, > giving an error when the name does not resolve (this is work for > an ISP ...) For the purpose of this email, you can just consider > these warnings the same as normal validators (well, ignore that > hard errors probably don't make sense with DNS) > > Now the point is, I really need to do asynchronous resolving, > i.e. start a bunch of resolver queries for all fields and then > collect the answers as they come. I'd like to do it that way: > > (1) The validator just starts the query, keeps a queue of all > existing queries, and returns normally. > > (2) After all validations have been run, all the answers are > collected, obeying a timeout. > > For the second step, I need a kind of hook that starts after > regular validation.
There is no signal dispatched in the manipulators, so your best bet would be to replace the get_validation_errors() method in the Manipulator class with your own method that calls the original method and then sends off any signal or further processing that you want to do. Since custom manipulators sub-class Manipulator, this is easy. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
