anchor.diff:  var cometd = dojox.cometd; // Use $.cometd if using jquery
   ...
   cometd.reload({
  -    cookieMaxAge: 15
  +    name: 'com.acme.Company.reload'
   });
   ----
   ====
  -
  -If you increase the `maxCookieAge`, be aware that you should probably increase
  -the value of `maxInterval` too (see also
  -<<_java_server_configuration,the server configuration section>>), to avoid the
  -server expiring the session while the page is reloading.
   
   ==== Understanding Reload Extension Details
   
  
positive.code: On page reload, or when the page is navigated to another CometD page, the
  application code must call `cometd.reload()` (for example, on the page
  _unload_ event handler, see note below). When `cometd.reload()` is called, the
  reload extension saves a short-lived cookie with the CometD session state details.
  When the new page loads up, it will execute the same code executed on the first
  page load, namely the code that configured CometD, that registered channel
  listeners, and that finally called `cometd.handshake()`.
  The reload extension is invoked upon the new handshake, sees that the short
  lived cookie saved previously is there, and re-establishes the CometD session
  with the information stored in the short lived cookie.
  
  [NOTE]
  ====
  
negative.code: browser window, hitting the browser back button or clicking on a link.
  
  As a rule of thumb, function `cometd.reload()` should be called from an
  event handler that allows to write to the `SessionStorage`.
  
  Typically the `window.onbeforeunload` event is a good place to call
  `cometd.reload()`, but historically the `window.onunload` event worked
  