Network Deployment (Distributed operating systems), v8.0 > Applications > Communications enabled applications > Communications Enabled Applications concepts

CEA collaboration flow

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.

1. User A initiates collaboration by clicking the collaboration widget, which sends a specific HTTP REST request.
2. The container calls the system application:

   • User A is placed in the user registry.

   • User A's session is established.

3. The response to User A includes a uniform resource locator (URI) for peers to start collaboration.

4. 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.

5. User B responds by sending a request with that URI.
6. 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.

7. A response is sent to User B.

   • Includes URI to exchange data.
   • Activates modal windows in each widget.

8. User B highlights text, scrolls, or fills in a form.

9. User B's widget sends these events through the send URI.
10. The container sends data to User A's session.

11. User A's widget polls for events with the fetch URI.

12. 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
Communications Enabled Applications concepts
Sharing data across two sessions with REST APIs
CEA call flow Concept topic

+

Search Tips   |   Advanced Search