...
| Section |
|---|
| Column |
|---|
| | Insert excerpt |
|---|
| US:_i_EDMthinClientDetails |
|---|
| US:_i_EDMthinClientDetails |
|---|
| nopanel | true |
|---|
|
|
| Column |
|---|
The figure to the left shows the main modules of the EDMthinClient. 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_EDMthinClientSymbol(200px) |
|---|
| US:_i_EDMthinClientSymbol(200px) |
|---|
| nopanel | true |
|---|
|
|
| Column |
|---|
The EDMremoteInterface is represented by the greyed gates TCP and HTTP. Note that the gates for LOCAL_DB og LOCAL_CONTEXT are not available with EDMthinClients. EDMthinClients have no local EDMdatabase to loop back to. |
|
|
|
| Section |
|---|
| Column |
|---|
| | Insert excerpt |
|---|
| US:_icon_Important(30px) |
|---|
| US:_icon_Important(30px) |
|---|
| nopanel | true |
|---|
|
|
| Column |
|---|
When writing EDMthinClient applications, it is important to be aware of a serious performance catch. Since the communication through the TCP and HTTP gates is stateless, there may be a significant overhead with each call to the EDMremoteInterface API function calls. E.g, looping over the elements of huge aggregates will require a restore of the state for each single call. A good way to handle situations like that would be to write your code in EDMexpressX, compile it into the EDMdatabase and execute the method with a single call to the EDMvirtualMachine. |
|
...
The following is a description of each of the modules in the block diagram.
...