Assist co-browse session is not a continuous flow of screenshots. Instead, data transmission is triggered by changes in shared display. Most common triggers are:
- Scroll bar use,
- Window resize
- HTML DOM Change or web page navigation.
On each trigger instead sending complete screenshot, only the difference with the last screenshot will be sent out from Consumer device to CafeX assist server. Cafex Assist server will then transmit the data to the other end point, i.e. Agent.
During a co-browse session if there is no display change in a given time frame, no data will be transmitted in that duration.
Bandwidth consumption for a co-browse session depends on:
- Content being shared, i.e graphics rich images Vs plain text articles.
- Resolution of the device being used by consumer, i.e. HD display Vs low resolution devices.
- Frequency of changes in the shared contents during co-browse session.
- Quantity of changes, i.e only part of the displayed area changing Vs the complete page refreshing.
Below is a throughput graph, for a sample co-browse session. This is just a sample to demonstrate data being transferred on navigation triggers.
Consumer device resolution: 1680 X 1050
This graph shows data being sent from Cafex server to Agent, same amount of data will be sent from Consumer to CafeX server.
For contents being shared as well as frequency of changes, see video recording: