tag:blogger.com,1999:blog-1280594010967081625.post3680955108357876777..comments2008-09-25T09:10:04.484-04:00Lateef Jacksonhttps://profiles.google.com/104965469689680679178noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1280594010967081625.post-32615849699372904682008-09-25T09:10:00.000-04:002008-09-25T09:10:00.000-04:00Calvin,<BR/>Yes you are completely correct. I use lighttpd (lighty) to proxy Appengine however this seems a bit crazy. I have to start both servers, make sure I have properly configured 2 things so I can have fast static file serving? I wrote my first static web site in 1995, with things like Dojo loading tons of files in development mode (don't get me started about there jacked up build system). Solution should be _simple_, I have to work on figuring out how to get my dynamic code fast but static code should be solved at this day and age.Lateef Jacksonhttp://www.blogger.com/profile/10815442680804512030noreply@blogger.comtag:blogger.com,1999:blog-1280594010967081625.post-81049554249833928672008-09-25T00:28:00.000-04:002008-09-25T00:28:00.000-04:00You seemed to suggest that because AppEngine didn't employ threads (at least, not exposed to the likes of us) that it was handling static files through the same processes. I don't know if this is the case, but it certainly doesn't need to be. Your YAML file maps some URLs to your script(s) and others to static resources, and it makes sense that they could take advantage of this to serve the static content through their undoubtedly optimized static file servers. They might even employ there scaling based on what URL patterns get the most traffic, so if you serve mostly static content it might be given more resources than those running your scripts.Calvin Spealmanhttp://www.blogger.com/profile/07161631946662126734noreply@blogger.com