Don't serve WAFileLibrary subclasses from Seaside
James Foster explains how to make the static parts of your Seaside app actually static:
Most of us recognize that static files do not need to be served from Seaside, but it is a step that can be easily overlooked. I was recently helping someone analyze performance for a Seaside application and we found that serving the initial page made 20 Seaside requests, all but one of them for something in /files (i.e., a subclass of WAFileLibrary). In this case it was Scriptaculous, but it could be anything.
Read the whole thing for details.
Technorati Tags: seaside
