The InvokeClient example demonstrates how to invoke a user defined method on:
These command line options start InvokeClient using the default metaspace named
ms and allow it to connect to a security domain controller that has been started using the example security policy file
example_policy.txt. Using the
-encrypt_field command line option allows
InvokeClient to connect to the same space defined when
ASOperations is started with security and the
-encrypt_field command line option.
After InvokeClient initializes, the following options are displayed that allow you to perform actions on the space:
The Invocable interface is used when the key option is selected. The
MemberInvocable interface is used when the
self,
seeders, or
members option is selected.
The purpose of the key option is to see that the user-defined method is invoked on the seeder that contains the entry with the key of 1. To see anything with the
key option, you should start up two instances of
ASOperations, using the
-role seeder command line option, and put some entries into the space, making sure that you have an entry with a key of 1.
When the example is run and the key option is selected, you will see the-user defined method of the Invocable interface run by the seeder that contains the entry with a key of 1.
The purpose of the other options is to let you see how the user-defined implementation of MemberInvocable is called on different members of the space. The
InvokeClient example joins the space as a leech. To see what happens when the user-defined method is invoked with these different options, start up two instances of
ASOperations, using the
-role seeder command line option, along with
InvokeClient. In this case: