With the 2016 Release of the PROLIN Smart Suite we have improved the transport of data between the Smart Client and the Power Server.
Use case: Net.Tcp & Http.lite
The legacy protocol for communications between the Client and the Server for HPSD is ITP*. This protocol has a number of disadvantages such as outdated compression methods.
With Smart Client 2016 we have introduced a number of alternative protocols that provide both performance and communication improvements.
The alternative protocols on offer are:
Basic Http Binding is used in scenarios where interoperability is of utmost importance. As a result, Basic Http Binding uses HTTP for the transport and encodes the message using Fast Infoset.
Configuration of net.tcp binding focuses on creating a channel stack that will perform better in Windows environments.
The net.tcp.lite transport is similar to net.tcp but (as its name implies) has some disabled binding options which could improve overall performance depending of the local network configuration.
How do we configure this?
In the server configuration make sure that the protocols are enable and the ports in the firewall(s) are opened.
In the Smart Client open the User options and use the â€œAuto Configurationâ€ button the Smart Client will determine the optimal protocol for your situation.
Once connected you can check the protocol used by hovering over the connection icon in the right lower corner of the Smart Client.
For more information please consult with your local PROLIN support representative.
*Interactive Terminal Protocol, an early Packet Assembler/Disassembler protocol for use on X.25 networks