Similarly, one would need to include semantics to accomodate broken internet explorer which cares about whitespace, comments, etc. (You could also remove comments.)
I think a more generalized way to implement this - if you really wanted to go there - would be to write a wsgi server - or the like - to do this in a middleware between the web app and the web server. You could write it in C - for speed - and it could be used for any web application/framework with minimal additional overhead as compared to incorporating this logic into Cherokee directly. Sorry for killing this feature-buzz, but this type of logic belongs outside the webserver layer - IMHO. Ryan On Thu, Feb 19, 2009 at 3:08 PM, Stefan de Konink <[email protected]> wrote: > Jordi Adame wrote: >> I know there are lots of frameworks that do this, the problem is those >> frameworks are not as fast as a webserver is doing this job, i've been >> using the strip module in nginx and it's so much faster than doing so in >> PHP. > > It might be worth the overhead to strip this when cached. But what do > you consider white space? And what not. In some elements like <pre> you > cannot do this. And this therefore involves semantics. > > I think gzip does a much better job at lossless compression ;) You want > lossy HTML, I wish you luck ;) > > > Stefan > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
