On Wed, 10 Nov 2010, Samuele Kaplun wrote: > Il giorno mer, 10/11/2010 alle 15.45 -0500, Benoit Thiell ha scritto: >> currently WSGI doesn't serve static files and Apache is responsible >> to do that. This causes several problems because static files and >> Python executables are mixed up in /var/www/admin/.
Yes, this is a known issue, and we have a branch almost ready that transforms all the mod_python URL handler driven admin pages into native Invenio URL handler driven admin pages, so `www/admin/' will be soon no more. (By soon I mean not in the forthcoming v1.0.0-rc0 yet, but in a future rc1 some time, before final v1.0.0 release.) <http://invenio-software.org/ticket/150> > Yes, serving static files via WSGI means serving static files via > Python, instead of via Apache which was born for this. Moreover it is > not optimized WRT I/O performances because every block of data that > need to be sent to the user is first read from disk and then sent to > the user. In Apache instead, when one block is sent to the user, the > next one is read at the same time. And, more importantly, when it is Apache that serves static files, Invenio WSGI daemon processes are free to run jobs for other users. So the separation is great for scalability purposes. Best regards -- Tibor Simko
