On Wed, Apr 8, 2009 at 1:26 PM, Jason Reid <[email protected]> wrote: > > Is that not going to kill Python; especially if I am serving enormous > files at high speeds to multiple users? It also needs to support > concurrent connections to the same resource as well as starting > offsets for download managers?
If the system will be serving disproportionately more static files than dynamic pages, then at some point Python will not be able to keep up, and you'll have to serve the files from Apache with a non-Python authorization system. WebKit was not designed for this situation. But if your static files are served at about the same rate as your dynamic pages, then you can serve them via FileApp and use your normal Pylons auth system. If the load is too much for Pylons to serve dynamic pages too, then you've got a bigger problem. Multiple servers may be an answer. Generally it's better to have the same authentication/authorization system for both dynamic and static files than to have a separate one for each. Otherwise it's a bunch of extra work and the possibility of accidentally configuring the two differently. If you go with a Python auth route, you'll have to serve the files in the controllers or add some custom middleware to StaticURLParser in middleware.py. If you go with a non-Python auth system, perhaps you can set it up to do everything but it depends on what you want. But if your authorization rules depend on Python data structures or you want to avoid using Apache modules whenever possible, you'd have to authorize in Python. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
