Web and WebWorks Development

[fdittz]

Hi.

We're developing an web-application that will be called by a widget, using the identity API.

We've noticed that apparently there's no caching at all when calling a external url on our widget app (all that it does is a post to an external url on our intranet). When we simply input this url on the native browser it's much faster (we even noticed some small rendering differences), and we can see the cache working.

I've seen some caching parameters to set in config.xml, but it seems that all is enabled by default.

Any ideas? Do I need to do something that I'm missing?

Thanks.

[tneil]

The Caching mechanism of a WebWorks/Widget app respect the response headers coming back from the web server.  If the server returns caching timeouts it will cache the items.

The existing caching mechanism doesn't parse and respect caching meta tags. I believe that if a server is returning no headers back, the application will cache the data.  However, if the server is returning no-cache for its items, then the application will not cache the item