RTC - set Minimum client-compatibility version afects Advisors building with old SDK?
I Use RTC Server in my company and I would like set Minimum client-compatibility version, but this configuration can affect the Advisors with SDK other versions? for example: I build Advisors using SDK 4.0.6 and deploy in my server. If I set this configuration for minimal version 5.0 this Advisor not work?
One answer
This is a server setting that I would rather not touch. I am puzzled why you even wanted to do that.
Client Compatibility is about clients, which means using the client API. The client API (Plain Java Client Libraries) have the version they are released for built in. This provides the information for checking version compatibility not your code. So you can only run your code on a different (older) Plain Java Client Library version to trigger this. The build system and the scm command line should check for compatibility as well, if I am not mistaken.
An advisor is typically a server extension and I am not sure it even touches the client compatibility version. All you can do to make the extension only work with certain versions is to manage the version compatibility in the manifest file.
Client Compatibility is about clients, which means using the client API. The client API (Plain Java Client Libraries) have the version they are released for built in. This provides the information for checking version compatibility not your code. So you can only run your code on a different (older) Plain Java Client Library version to trigger this. The build system and the scm command line should check for compatibility as well, if I am not mistaken.
An advisor is typically a server extension and I am not sure it even touches the client compatibility version. All you can do to make the extension only work with certain versions is to manage the version compatibility in the manifest file.