A Communications Enabled Applications (CEA)
Web collaboration
session allows dynamic interaction between users sharing linked browser
sessions. Users connect their Web sessions using the CEA collaboration
widget. Use the collaboration flow illustrated in this topic to understand
how live Web collaboration works.
- User A initiates
collaboration by clicking the collaboration
widget, which sends a specific HTTP REST request.
- The container
calls the system application:
- User A is placed in the user
registry.
- User A's session is established.
- The
response to User A includes a uniform resource locator (URI)
for peers to start collaboration.
- User A sends User B the
"for peer collaboration URI."
- The "for peer collaboration
URI" contains a nonce,
a unique identifier which is particular to the collaboration session.
The nonce helps ensure security in the collaboration session.
- User B responds by sending a request with that URI.
- The
container calls the system application:
- User B is placed in
the user registry.
- User A is found in the user registry.
- A "link" is established between them.
- A response
is sent to User B.
- Includes URI to exchange data.
- Activates
modal windows in each widget.
- User B highlights
text, scrolls, or fills in a form.
- User B's widget sends these
events through the send URI.
- The container sends data to User
A's session.
- User A's widget polls for events with the fetch
URI.
- User B's events are captured in User A's widget.
The following diagram shows the collaboration flow between linked
user sessions.
Figure 1. CEA Web collaboration