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 nothing is done with the peer's reported protocol version number. Transport.getRevision() is always returning PVAConstants.PVA_PROTOCOL_REVISION when it should be returning the lesser of this or remoteTransportRevision.
So far, monitor flow control messages have been conditional on a pvRequest option 'record._options.pipeline'.
This requires the client to implicitly know if the server supports this protocol feature.
I'm planning to make monitor flow control messages mandatory, and to use a minor version increment to signal this in a backwards compatible way.
The text was updated successfully, but these errors were encountered:
Right now nothing is done with the peer's reported protocol version number. Transport.getRevision() is always returning PVAConstants.PVA_PROTOCOL_REVISION when it should be returning the lesser of this or remoteTransportRevision.
So far, monitor flow control messages have been conditional on a pvRequest option 'record._options.pipeline'.
This requires the client to implicitly know if the server supports this protocol feature.
I'm planning to make monitor flow control messages mandatory, and to use a minor version increment to signal this in a backwards compatible way.
The text was updated successfully, but these errors were encountered: