anchor.diff:  In both Dojo and jQuery extension bindings, the extension is registered
   on the default `cometd` object under the name "reload".
   
  +[[_extensions_reload_configuration]]
   ==== Configuring the Reload Extension
   
   The reload extension accepts the following configuration parameters:
  
positive.code: | Default Value
  | Parameter Description
  
  | cookieName
  | org.cometd.reload
  | The name of the short-lived cookie the reload extension uses to save the connection state details
  
  | cookiePath
  | /
  | The path of the short-lived cookie the reload extension uses
  
  | cookieMaxAge
  | 5
  | The max age, in seconds, of the short-lived cookie the reload extension uses
  |===
  
  The JavaScript `cometd` object is normally already configured with the
  default reload extension configuration.
  To reconfigure the reload extension:
  
  * Reconfigure the extension at startup:
  +
  
negative.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 the CometD session state details in the
  https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage[`SessionStorage`]
  under the name specified by the <<_extensions_reload_configuration,configuration>>.
  
  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, will find the CometD
  session state saved in the `SessionStorage` and will re-establish
  the CometD session with the information retrieved from the `SessionStorage`.
  
  [NOTE]
  ====
  