Client Services Transport Protocols |
Open Client Administration |
 |
|
Client Services Transport Protocols |
Open Client Administration |
|
The PROIV Client offfers a choice of transport protocols for communication between the Client and the Server. The original protocol was the standard internet HTTP Response\Request messaging. This has now been replaced as the default protocol by WebSockets.
WebSockets open up a two-way communication channel that allows messages to be sent to the Server along with receiving responses without having to poll the Server for a reply. The HTTP protocol sends a Request message, then has to poll the Server for whether the Response is ready.
WebSockets have the advantage of potentially being quicker communicating, avoiding any lag while polling takes place. Replacing the HTTP Request/Response model with WebSockets therefore removes restrictions as to when the Server communicates with the Client or vice versa. The WebSocket protocol passes the same Commands, Events and JSON payload as HTTP uses for communications between Server and Client. WebSockets have the benefit that if messages arrive from the Virtual Machine when we weren't expecting them we will now be able to inform the Client about them. When using HTTP those messages are not processed immediately but only when another action has been taken.
One possible downside of using a WebSocket is the need to maintain a further thread per session. The activity on this thread can be adjusted by setting the Poll Interval timing value on the Dashboard for the Client Service.
Both transport protocols are available for Lite Client and Open Client.
Topic ID: 840004