...
| Section |
|---|
| Column |
|---|
| | Insert excerpt |
|---|
| US:_i_EDMstandaloneClientDetails |
|---|
| US:_i_EDMstandaloneClientDetails |
|---|
| nopanel | true |
|---|
|
|
| Column |
|---|
The figure to the left shows the main modules of the EDMsdk. In the following, we will give a brief description of each module. When drawing system diagrams for EDMsix, a simplified block is used to represent the EDMstandaloneClient. | Section |
|---|
| Column |
|---|
| | Insert excerpt |
|---|
| US:_i_EDMstandaloneClientSymbol(200px) |
|---|
| US:_i_EDMstandaloneClientSymbol(200px) |
|---|
| nopanel | true |
|---|
|
|
| Column |
|---|
The EDMremoteInterface is represented by the four greyed gates. TCP, HTTP, LOCAL_DB and LOCAL_CONTEXT |
|
|
|
The following is a description of each of the modules in the block diagram.
EDMInterface Language Bindings
...
| Section |
|---|
| Column |
|---|
| 
|
| 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 only available if you have an EDMsdk license on your system. It is these gates that make it possible to write EDMstandaloneClient applications with the EDMremoteInterface API. The two gates loop every call back to the local EDMdatabase that is opened by the EDMstandaloneClient |
|
...
EDMsix Core
| Section |
|---|
| Column |
|---|
| 
|
| Column |
|---|
| This is the very core of the EDMsix platform of Express Data Manager. It contains the EDM Compilers and debuggers, The STEP and XML import/export modules, the EDMvirtualMachine with EDMmodelConverter, EDMmodelChecker and EDMqueryEngine, the memory manager, the access control system and virtually any other core feature in EDMsix. This is the component that is included in every EDMsix product. |
|
...