On 28 Led, 15:20, Ned Batchelder <n...@nedbatchelder.com> wrote: > Almad, you've pointed to ticket 10117 a few times now, but I don't see > how this has anything to do with a single-threaded server. I think if > you could clarify that point, maybe we'd be able to make some progress > on this.
True, I just got that feeling from 'multithreading fixed it for me', but I'll do some more tracing later. > The core devs are not going to change their mind about multi-threading > the development server, so please stop asking them to. OK. > The disagreement > on the table now is whether you have a common problem here, or an > esoteric one. When I look at the code in 10117, there doesn't seem to > be anything multi-threaded about it. That's good news for you, because > it may bring your problem into the category of "will be fixed" from > "won't be fixed". If you could help us understand your precise problem > more, and by that I mean give us more information about where you think > the multi-threading is coming from, or otherwise explain the connection > reset, then we could all get beyond the mud-slinging. OK, I'll investigate it deeper, because from http://code.djangoproject.com/ticket/10117#comment:4 , it looks like it might be a wsgi bug. What puzzles me is, that if I recall my debugging correctly, this bug was fixed for me even without using CP WSGI, just multithreading Django's one. > --Ned.http://nedbatchelder.com Almad --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
