Editing Common NetMsg Exchanges
From BRL-CAD
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | + | {{DesignDocument}} | |
− | + | ==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. | |
− | |||
− | |||
− | |||
− | + | # 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. | ||
+ | # 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. | ||
+ | |||
+ | ==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. |