Our release notes always describe whether there are any changes that may affect compatibility:
https://guacamole.apache.org/releases/ You will need to check the release notes for the versions that follow the release you're using to see whether any changes might affect you. Since you are way back in 1.0.0, you have a fair amount of reading ahead of you, but there are dedicated sections of the release notes for these kinds of changes. Changes are not made to the protocol in 1.x releases in a way that would break compatibility with older 1.x releases. For example, see: https://guacamole.apache.org/releases/1.4.0/#deprecation--compatibility-notes - Mike On Thu, Feb 9, 2023, 4:59 PM Carlos Villegas <[email protected]> wrote: > Just a general question, > > We have a (now fairly old) application using guacamole 1.0.0. We had > written a custom frontend for Vaadin 8 using the Guacamole common > javascript client and it's been working well enough that it hasn't been > kept up to date with the latest Guacamole version. I'd like the thank the > Guacamole developers and community for the excellent product! > Anyway, there were some issues with keyboard mappings, specifically the > CAPS LOCK key not working, that seemed to have been fixed already. I did a > quick test of just upgrading the guacd proxy to the 1.4 version. Apart from > some minor configuration changes like forcing the security mode to > accommodate our old RDP server, it seems to be working fine with our old > client frontend and the keyboard mapping issues are now solved! > My question is whether using the old client with the new proxy will bring > some issues due to incompatibilities in the guacamole protocol between > client and proxy. So far I haven't found any. Or if the protocol itself has > been stable from 1.0 to 1.4? > > Thanks for any information about this, it will help us plan our migration > strategy. > > Carlos >
