BTW, in web2py we have:
- response.minify_css and response.minify_js (can compact css and js to a
single file, at runtime)
- response.static_version (adds far in the future cache headers so the
assets are downloaded only once)
- response.files support for any URL (i.e., you can stop using
response.files.append(URL('static', 'js/jquery.js')) and embed a CDN hosted
version with
response.files.append('http://ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js')
- if a version of the static file is compressed with gz and is found on the
same path, it's served that instead of the decompressed one (i.e.
myfile.css and myfile.css.gz)
The only thing missing is automatic compression of the dynamic content,
thing that is better leave to a proper webserver to handle.
Anyway, if you need those kind of heavy optimization, you'll probably end
up compressing/modularizing/minifying/CDNing your assets through an
external tool or by hand, or using a js loader directly on the html page
and orchestrate all from there (web2py (or any other web framework) doesn't
get involved with client-side computations)
Those are more "how to structure my web project" advices than "your
framework is poor if it doesn't support this". Anyway, as always, is up to
you exploit the possibilities, but web2py for sure doesn't get in your way.
On Wednesday, October 24, 2012 2:03:24 PM UTC+2, Marco Tulio wrote:
>
> At this Google page
> https://developers.google.com/speed/
>
> They talk a little about PageSpeed (Apache Module), PageSpeed Insights,
> good practices for web development and even about hosted libraries (as a
> way of making web faster).
>
> I'd like to know what you guys think about this, about what we already use
> and have implemented on web2py, what's worth doing, what's not, and so on.
>
> Hoping for some insights.
>
> Cheers!
>
> --
> []'s
> Marco Tulio
>
--
