You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now it doesn't look like stompest properly supports version negotiation.
StompConfig only supports a single version. And trying to use the versions parameter to connect on the sync client results in: StompProtocolError: Invalid versions: ['1.1'] [version=1.0]
Also ideally when version(s) is left as None we should not default to 1.0. Instead in that case we should include every version natively supported by stompest into accepts-version. And then use the version specified by the server in the CONNECTED header. So we can properly use the most recent version supported by both the server and stompest.
The text was updated successfully, but these errors were encountered:
You obtain the desired behavior by specifying StompConfig(uri, version=StompSpec.VERSION_1_2). I think that an implicit upgrade of the STOMP versions is not a good idea because you lose control over the features which are in use, and not all protocol changes are fully backward compatible. If you use the latest of StompSpec.VERSIONS, the definition StompConfig(uri, version=StompSpec.VERSIONS[-1]) of the config becomes generic.
Right now it doesn't look like stompest properly supports version negotiation.
StompConfig
only supports a single version. And trying to use the versions parameter to connect on the sync client results in:StompProtocolError: Invalid versions: ['1.1'] [version=1.0]
Also ideally when version(s) is left as None we should not default to 1.0. Instead in that case we should include every version natively supported by stompest into accepts-version. And then use the version specified by the server in the
CONNECTED
header. So we can properly use the most recent version supported by both the server and stompest.The text was updated successfully, but these errors were encountered: