On 06/15/06 14:59, Jos Yule wrote: > I haven't plugged any of this into a twisted app yet, so i don't know.
I'ld be very interested to here how it's going once you get there. > I suppose i could put the db stuff into one of the threading defereds > to avoid that kind of blocking... > That's exactly what I'm doing atm. It gets sort of complicated though if you've got related models, 'cause of the lazy loading in querysets. You have to totally isolate any django related function/method calls, cause you never know for sure when/how/where the database is hit. If you find a better way I'ld love to here. Good luck --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
