This section describes the changes that have occurred in the way the connection protocol generates messages on the component side. It recalls the former behavior and describes the new one.

In Rogue Wave Server 5.1, when you use the class IlsIlvTcpMvProcess on Microsoft Windows® platforms, the connection protocol generates two messages on the component side whereas it generates three messages if you use that class in a non-graphical application. This behavior is not correct: in both cases, three messages should be received on component side.

With Rogue Wave Server 5.2, the connection protocol sends three messages to the component, whether you use IlsTcpMvProcess or IlsIlvTcpMvProcess.

If you were using IlsMvProcess::Run(2) to explicitly receive these messages in a graphical component, you have to replace this code by IlsMvProcess::Run(3).

These methods where called before and after a request from the network was processed, except for the connection and disconnection events which the sever handled by the server without calling these methods.

These methods are invoked also when connection and disconnection events are received.