Following 1.6.2, when the network send is too large, Iris-Server no longer opens a message window to inform the user of this fact prior to closing. Instead, Iris-Server stops sending further viewports with a size greater than or equal to the failing viewport size. This can cause the client image to appear to not start, freeze, or in rare situations stutter if the size of the JPEG captured is close to the maximum value.
This issue is to introduce logging of the Iris messages to make the user better aware of the message size limitation.
The action in the case of viewports being too large to be sent is to capture the screen area as two (or more|) adjacent viewports.
Following 1.6.2, when the network send is too large, Iris-Server no longer opens a message window to inform the user of this fact prior to closing. Instead, Iris-Server stops sending further viewports with a size greater than or equal to the failing viewport size. This can cause the client image to appear to not start, freeze, or in rare situations stutter if the size of the JPEG captured is close to the maximum value.
This issue is to introduce logging of the Iris messages to make the user better aware of the message size limitation.
The action in the case of viewports being too large to be sent is to capture the screen area as two (or more|) adjacent viewports.