Re: [Cppcms-users] Multiple class of render()

[<ele...@ex...>]

>> Ok, but shouldn't the JS/CSS be cached on the client anyway?
>>
> It should, but dont ask me what chrome is doing in the end.

Are you running the application from the built in http server? Or are you
using fastcgi/nginx ?

I believe the built in http server sends only minimal headers. It doesn't
send Last Modified or any other caching headers. It got me by surprise
also. But it makes sense. During development you're unlikely need any
caching at all and thats what the built in http server was designed for.

> Also I need to support different screen resolutions (qvga and vga) -
> done via html
> body id and css. So I don't see that much sense in caching so dynamic
> pages, but
> may I be wrong :)

Well I never had to do this but, if the above works for you (the CSS/JS
caching). With the cppcms cache you're caching the content.

Provided that:
1) You can cache JS/CSS files in chrome
2) Most of your JS/CSS is is not inline with HTML
3) The rest you can cache on the server side

I think you shouldn't need PJAX at all. Judging by the difference in speed
you get due to not loading JS/CSS on every page load, that is likely your
bottleneck.

Petr