* josef reidinger <jreidinger@suse.cz> [Jun 24. 2009 11:21]:
Klaus Kaempf napsal(a):
The rest-servicce backend should not cache anything since it is meant to be stateless. The web-client should only hold the session cookie for caching the login credentials.
I think that caching in web-client is not so bad, if you cache "constants".
Agreed. And making resource cacheable is one of the core features of REST. But its actually up to the rest-service to indicate the lifetime of the resources via the http header. The web-client should honor this information.
Of course you can define constants directly in this module, but it is possible that that constant is changed sometime (less then once per month). For example possible timezones is quite big data, which doesn't change much often. So I cache it in web-client to save some transfer and to increase performance (waiting more then second to after every action on web page is to much for me).
Now such caching should be done in the resource proxy within the web-client. It doesn't belong to the session cache because it can be shared across sessions. Don't get me wrong here. I'm all for caching. But we need to be careful on what, when, and how resources get cached. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org