Hi, On Thu, Jan 29, 2009 at 3:45 PM, Graham Dumpleton < [email protected]> wrote:
> > FYI, there is a discussion over on: > > > http://jtauber.com/blog/2009/01/26/serving_up_user_contributed_media_from_a_separate_server/ > > about best way of serving up files previously downloaded to application. > > My suggestion was that generating X-Sendfile for nginx front end to > handle might be best as far as performance and not loading up Apache. X-Sendfile is very similar to the Perlbal way of doing it (x-reproxy-file]) - its a nice solution for authenticated/restricted access to static data (PDFs/images/whatever) - Django just decides what resource you're getting or not, then nginx/etc does the actual work. We've also done some chained stuff: - django figures out the access to the resource - then an internal redirect to the resource - if the resource doesn't exist, it passes another internal redirect - to a service that generates it, stores it for later access, then returns it In my case the generator services can be very memory or CPU hungry, so we don't want to do it on the main web/static servers. Rob :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
