Trace:
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
jvx:communication:connections [2018/02/01 10:35] admin created |
jvx:communication:connections [2018/02/01 10:55] admin |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| In this case the DirectServerConnection is used, which means that server functions are called directly via the server class and objects are passed on to methods directly. There is no serialization, which positively affects performance. | In this case the DirectServerConnection is used, which means that server functions are called directly via the server class and objects are passed on to methods directly. There is no serialization, which positively affects performance. | ||
| - | <fs 20px>Note</fs> | + | \\ |
| + | **<fs 20px>Note</fs>** | ||
| At no point the developer has to take the communication protocol into account, since it is encapsulated by JVx. However, we have to be aware of the difference in operation between DirectServerConnection and VMConnection or HttpConnection, since the object serialization has to be considered during troubleshooting. | At no point the developer has to take the communication protocol into account, since it is encapsulated by JVx. However, we have to be aware of the difference in operation between DirectServerConnection and VMConnection or HttpConnection, since the object serialization has to be considered during troubleshooting. | ||