Re: A Responsive Single Page App (SPA) with 3 Issues to Consider

One thing I have grown to dislike about having a single page app is
browser caching.

Default behavior under RFC is for browsers to cache content returned by the
HTTP GET method, which applies to all content, whether static or
dynamically generated.

In other words, caching is not unique to SPAs. It's is universal unless
overridden by:

a. adding something to a URL to make it unique.
b. embedding cache-control headers in the response.

SPA's make requests via AJAX, where the xmlHTTPRequest object can also be
used to override caching:

xmlHttpRequest.setRequestHeader("Cache-Control","no-cache");

I'm not sure if JQuery has a way of evoking the setRequestHeader() mehod,
but developers should be aware that it's available.

Default behavior under RFC is for browsers to NOT CACHE content returned by
the HTTP POST method. But that behavior can likewise be overridden by
"header" directives.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.