Common NetMsg Exchanges

This page contains the design document for an enhancement or feature. The design should be considered a work in progress and may not represent the final design. As this is a collaborative design, contributions and participation from other developers and users is encouraged. Use the discussion page for providing comments and suggestions.

Application Interconnect Handshake

This sequence of NetMsg exchanges represents the communications between an external application (App M) attempting to connect to a running Geometry Service (App GS). This sequence assumes success.

Main Sequence

1. App GS waits for incoming socket requests.
2. App M creates a socket connection to App GS.
3. App GS accepts the socket connection.
4. App M and App GS are now connected at the socket level.
5. App M sends a RemHostNameSET NetMsg to App GS.
6. App GS checks its RemHostName list for duplicates. (Alt #1)
7. App GS sends a RemHostNameSETOK NetMsg to App M.
8. App GS sends a RemHostNameSET NetMsg to App M.
9. App GS waits for App M to send a RemHostNameSETOK NetMsg.
10. App M sends a RemHostNameSETOK NetMsg.
11. App M is now connected to the Geometry Service network.
12. App M sends a NewSessionREQ NetMsg.
13. App GS creates a new Session.
14. App GS sends a NewSessionREQOK NetMsg.

Alt Sequence #1

6a. App GS finds that the incoming Host is already on the HostList. Either a duplicate name, or a duplicate connection.

6b. App GS sends App M a RemHostNameSETFAIL NetMsg.

6c. App GS drops socket connection to App M.

6d. App M drops socket connection to App GS.

Application Request For Geometry

This sequence of NetMsg exchanges represents the communications between an external application (App M) as it requests Geometry from the Geometry Service (App GS). This sequence assumes success.