On Feb 11, 12:06 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> The files will be stored on a general > filesystem (probably on a large SAN array but I appreciate advice on > alternatives that can be shared by multiple servers). An alternative to SAN would be MogileFS (from the same people as perlbal and memcachd). It lets you distribute files over cheap disks that can scale out with your other servers. It offers redundancy across servers instead of using RAID. http://www.danga.com/mogilefs/ > 1. What's the current best practice/preferred web server for serving > lots of static content (upload and download) quickly and efficiently? > Is Tux the way to go? LightTPD (aka Lighty) is a popular web server for static content. Its used by some big players such as YouTube and Wikipedia. http://lighttpd.net/ > 2. I understand that most static content servers get a lot of their > speed because they can't handle dynamic content. How do I ensure they > will properly call the authentication&authorization system before > starting the download/upload? I don't have any experience of this, but Lighty has a module called mod_secdownload that lets you handle authentication/authorization in your application then generates a unique url and redirects the client to download (fast) from that url. http://trac.lighttpd.net/trac/wiki/Docs%3AModSecDownload Scott --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
