The Resource History is a temporary cache of all data (DOM, CSS, images, etc) generated during an in-context session. The Resource History is the filter-related functionality that ensures that everything seen in the visitor browser can be seen in the agent browser. If you picture the Resource History as more than just a cache but as a replication machine, or resource replicator, that ensures everything (all resources) in the visitor browser can be replicated on the agent browser, securely, then you will better understand whether or not you require the Filter’s Resource History functionality (in order that your agents can see what the visitor sees, seamlessly and securely).
When a co-browsing session is started and the visitor browser requests images from your organization’s backend, the Installing the SecureFlow Manager (Filter) is triggered as soon as the response arrives at the proxy. So, while the backend is supplying images to the visitor browser, the Installing the SecureFlow Manager (Filter) duplicates that content and uploads it to the Collaboration Server (which then passes it to the agent browser).
Note: Without the presence of the Installing the SecureFlow Manager (Filter) within the filter chain it is impossible to view session-specific data. The absence of the Installing the SecureFlow Manager (Filter) will not break the session but any image content generated specifically for that session will simply not appear in the Agent’s browser.
Note: The default behavior is that the DOM and image data is stored in temporary memory for the duration of a session. It is not stored permanently.
- The Resource History is: A cache of all data generated during an in-context session.
- An in-context session uses a method we call ‘Embedded Co-browsing’.
- Embedded co-browsing may require the Installing the SecureFlow Manager (Filter).
For more on Resource Histories see: Resource Histories Technical Detail.