...
The following is a description of each of the modules in the block diagram.
EDMInterface Language Bindings
| Section |
|---|
| Column |
|---|
| 
|
| Column |
|---|
The EDMInterface Language Bindings are implemented with the EDMremoteInterface API. The following language bindings are available; C, C++, Java, VisualBasic and .NET |
|
EDMInterface API and EDMsix Core
| Section |
|---|
| Column |
|---|
|  Image Modified
|
| Column |
|---|
For EDMthinClient applications, the EDMInterface API and the EDMsix Core is not in use and need not even be activated by an EDMsdk license. Note that there is no local EDMdatabase either. |
|
EDMremoteInterface API
| Section |
|---|
| Column |
|---|
| Image Modified |
| Column |
|---|
The EDMremoteInterface API is available without an EDMsdk license. EDMthinClient applications must use this API to access the TCP and HTTP communication ports. All EDMremoteInterface API functions take the Server Context input parameter to specify the information required to connect to an EDMsixServer. The two ports LOCAL_CONTEXT and LOCAL_DB are not used by EDMthinClients. EDMthinClients have no local EDMdatabase to loop back to. With no EDMsdk, the EDMremoteInterface is reduced to a module that transfers parameter sets to the EDMsixServer in TCP/IP blocks and recei.ves execution results from the EDMsixServer. The actual execution is performed entirely on the EDMsixServer side |
|
...