Hi all! I have a big problem, and after reading tons of web pages I'm still stuck.
IN SHORT: I'm on a shared server hosting with fastCGI (=no apache access) with no mod_xsendfile. I need to serve mp3 files of 2-3 minutes length after authentication. That view generates extra proccesses that never die, and maybe it timesout and creates new proccesses (???). THE DETAILS: My django app is on a share server, so I'm forced to use fastCGI. I don't have access to apache settings. Lately I've been having lots of proccesses named "/usr/bin/python index.fcgi" that suddenly appeared and just stayed there forever. After a lot of headache, I figured out their source was an HTML page with JPlayer plugin (a JQuery plugin to play music - http://jplayer.org). As the HTML page loads, Jplayer loads and calls my server with the URL of the music file to play. This request goes to this django view (needed for authentication of request): def serveMusicFile(request,filename): my_auth_check(request) from django.conf import settings file = open('/my/private/file/location/'+filename) response = HttpResponse(file.read(), mimetype="audio/mpeg") response['Accept-Ranges'] = 'bytes' response['Content-Length'] = os.path.getsize('/my/private/file/ location/'+filename) response['Content-Disposition'] = 'filename='+filename return response So, Why does the fastCGI create new threads for these music file requests? Why don't they die eventualy? **What can I do??** Thanks guys! -- 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.
