The ping example includes two entities: client and server.
The server entity provides two identical Ping and Pong methods that receive a number and return a modified number.
Ping(in UInt32 value, out UInt32 result);
Pong(in UInt32 value, out UInt32 result);
The client entity calls both methods in a different sequence and/or at different times. If the method call is denied by the security configuration, the Failed to call... message is displayed.
The transport part of the ping example is virtually identical to its counterpart in the echo example. The only difference is that the ping example uses two methods (Ping and Pong) instead of one.
Use of IPC transport is briefly examined in the ping example because it was already examined in detail in the comments to the echo example.
Using different security configurations
The ping example lets you use different security configurations to control interactions between the client and server entities. The calls of the ping() and pong() functions were put into the test() function whose implementation is contained in the test.c file. For this reason, you do not need to change the client.c code to demonstrate a different security configuration. All you need to do is edit (or replace) test.c.
The ping example contains security configurations (security.cfg) based on the flow and era families and the test.c files for these configurations.
Components of the ping example
The ping example consists of the following files:
client.cclient.edlserver.cserver.edl, ping.cdl, ping.idlinit.yamlsecurity.cfg (for the flow or era family)test.c (for the flow or era family)ping.era (only for the era family)