Difference between revisions of "Common NetMsg Exchanges"
| Line 1: | Line 1: | ||
{{DesignDocument}} | {{DesignDocument}} | ||
| − | ==Application Interconnect | + | ==Application Interconnect Connect== |
This sequence of [[IBME_GeometryService#NetMsg_Class|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. | This sequence of [[IBME_GeometryService#NetMsg_Class|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. | ||
| Line 28: | Line 28: | ||
==Application Request For Geometry== | ==Application Request For Geometry== | ||
| − | This sequence of [[IBME_GeometryService#NetMsg_Class|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 and that both App M and App GS have completed the Application Interconnect | + | This sequence of [[IBME_GeometryService#NetMsg_Class|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 and that both App M and App GS have completed the Application Interconnect Connect. |
===Main Sequence=== | ===Main Sequence=== | ||
| Line 39: | Line 39: | ||
:2a. App GS does NOT find requested Geometry. | :2a. App GS does NOT find requested Geometry. | ||
:2b. App GS sends App M a [[GeometryREQFAIL]] [[IBME_GeometryService#NetMsg_Class|NetMsg]]. | :2b. App GS sends App M a [[GeometryREQFAIL]] [[IBME_GeometryService#NetMsg_Class|NetMsg]]. | ||
| + | |||
| + | |||
| + | |||
| + | ==Application Interconnect Disconnect== | ||
| + | This sequence of [[IBME_GeometryService#NetMsg_Class|NetMsg]] exchanges represents the communications between an external application (App M) and a Geometry Service (App GS) during a disconnect event. The disconnect event can be generated by either side as the effect will be the same. This sequence assumes success and that App M initiates the disconnect event. | ||
| + | |||
| + | ===Main Sequence=== | ||
| + | # App M prepares all data for an impending disconnect event. | ||
| + | # App M sends a [[DisconnectREQ]] [[IBME_GeometryService#NetMsg_Class|NetMsgs]] to App GS. | ||
| + | # App GS receives the [[DisconnectREQ]] | ||
| + | # App GS prepares all of its data for an impending disconnect event. | ||
| + | # App GS closes the associated socket and removes the associated [[IBME_GeometryService#Connection_Class|Connection]] | ||
| + | # App M detects the closed socket. | ||
| + | # App M and App GS are disconnected. | ||
Revision as of 09:01, 4 December 2008
|
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. |
Contents
Application Interconnect Connect
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
- App GS waits for incoming socket requests.
- App M creates a socket connection to App GS.
- App GS accepts the socket connection.
- App M and App GS are now connected at the socket level.
- App M sends a RemHostNameSET NetMsg to App GS.
- App GS checks its RemHostName list for duplicates. (Alt #1)
- App GS sends a RemHostNameSETOK NetMsg to App M.
- App GS sends a RemHostNameSET NetMsg to App M.
- App GS waits for App M to send a RemHostNameSETOK NetMsg.
- App M sends a RemHostNameSETOK NetMsg.
- App M is now connected to the Geometry Service network.
- App M sends a NewSessionREQ NetMsg.
- App GS creates a new Session.
- 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 and that both App M and App GS have completed the Application Interconnect Connect.
Main Sequence
- App M sends a GeometryREQ NetMsg to App GS.
- App GS finds the request Geometry. (Alt #1)
- App GS sends App M a GeometryMANIFEST NetMsg.
- App GS sends App M as many GeometryCHUNK NetMsgs as required in order to fulfill the GeometryMANIFEST.
Alt Sequence #1
- 2a. App GS does NOT find requested Geometry.
- 2b. App GS sends App M a GeometryREQFAIL NetMsg.
Application Interconnect Disconnect
This sequence of NetMsg exchanges represents the communications between an external application (App M) and a Geometry Service (App GS) during a disconnect event. The disconnect event can be generated by either side as the effect will be the same. This sequence assumes success and that App M initiates the disconnect event.
Main Sequence
- App M prepares all data for an impending disconnect event.
- App M sends a DisconnectREQ NetMsgs to App GS.
- App GS receives the DisconnectREQ
- App GS prepares all of its data for an impending disconnect event.
- App GS closes the associated socket and removes the associated Connection
- App M detects the closed socket.
- App M and App GS are disconnected.