Hello! I'm looking for help from someone who is familiar with how FastCGI works.
I'm using well-known flup's FastCGI server. The app serves large files (mp3 albums, 100 MB typically) that users download with download managers that often drop connections on client side and start new ones. The strange thing is that when a client drops connection flup's FastCGI server seems to not notice it and keeps feeding output (somewhere?). This results in two bad things form me: server overload because of many working processes that work for nothing and my app thinking that the download went OK and registering it for the user even if the download went to nowhere. When I was running the same thing under Apache with mod_python dropping connection resulted in mod_python choking about "write error" immediately and my app knew that the download has stopped. So the question is where to start digging for the cause? I read some flup's code and found out that by default it should make unbuffered output right into its connection with the web server. And it looks like when the connection is dropped writing should fail. But it's not what's going... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
