2 ms·
There is client-side XSLT already. The problem is that transformed template is usually same size or smaller than your source data. Really expensive algorithms
by pornel 16y ago
There is client-side XSLT already. The problem is that transformed template is usually same size or smaller than your source data.
Really expensive algorithms aren't that much better to offset cost of sending template logic to the client.
You could probably save some processing time by integrating compression directly into server-side templating - take advantage of the fact that some parts never change and keep them pre-compressed or at least cache some statistics about them to aid compression.