08-30-2012, 05:39 PM
Though it's been in the protocol for some time, I somehow managed to never actually handle the logoff message in the RIVA server. I added that for the 4.2.5 release that I just posted today as the new official version.
So the client vendor guys can now send the logoff message just before you close down the socket so that the server knows that it's a graceful logoff and not a loss of connection, and not log a connection lost error message. Nothing comes back, the server just knows it should stop using the socket and close it down. If you send it to an older version of CQC that doesn't support it, it'll just get ignored.
Also, in terms of end users, if any of you haven't been reading the thread in the Support area about the post-4.2.0 follow up release (which lead to the 4.2.5 version I just posted) you may want to give it a try. It can provide significant performance improvements, according to the size/configuration of your CQC system. Some folks will see not huge but welcome improvements. Some will see major performance increases, and that can extend to RIVA clients indirectly. There weren't any changes in the RIVA system, but the system overall is performing so much more quickly that you can see good benefits for RIVA clients as well, and since the RIVA server hosts multiple interface viewer engines, it can benefit quite a bit from the improvements.
So the client vendor guys can now send the logoff message just before you close down the socket so that the server knows that it's a graceful logoff and not a loss of connection, and not log a connection lost error message. Nothing comes back, the server just knows it should stop using the socket and close it down. If you send it to an older version of CQC that doesn't support it, it'll just get ignored.
Also, in terms of end users, if any of you haven't been reading the thread in the Support area about the post-4.2.0 follow up release (which lead to the 4.2.5 version I just posted) you may want to give it a try. It can provide significant performance improvements, according to the size/configuration of your CQC system. Some folks will see not huge but welcome improvements. Some will see major performance increases, and that can extend to RIVA clients indirectly. There weren't any changes in the RIVA system, but the system overall is performing so much more quickly that you can see good benefits for RIVA clients as well, and since the RIVA server hosts multiple interface viewer engines, it can benefit quite a bit from the improvements.
Dean Roddey
Explorans limites defectum
Explorans limites defectum