Yes, it's backward compatible down to the oldest version supported. It is would always be recommended to the work with endpoint of the current release.
As you stated, new features are naturally unsupported on versions and endpoints w/o them and previous versions would be more exposed to issues fixed in later versions.
What is the oldest version support as far as 4.4 is concerned? The problem with the REST API is that with the version embedded in the URL we have to make code changes for every release. Back when we used the CLI we generally had upward compatibility over many releases so we only changed when we needed a new feature. If the REST is back compatible for multiple releases that will be fine. The issue is that if we upgrade we will then NOT work with older versions.
Idan
3 Apprentice
•
675 Posts
0
September 27th, 2016 05:00
Hi there,
Yes, it's backward compatible down to the oldest version supported. It is would always be recommended to the work with endpoint of the current release.
As you stated, new features are naturally unsupported on versions and endpoints w/o them and previous versions would be more exposed to issues fixed in later versions.
Regards,
Idan Kentor
RecoverPoint Corporate Systems Engineering
idan.kentor@emc.com
GKG12345
21 Posts
0
September 27th, 2016 05:00
What is the oldest version support as far as 4.4 is concerned? The problem with the REST API is that with the version embedded in the URL we have to make code changes for every release. Back when we used the CLI we generally had upward compatibility over many releases so we only changed when we needed a new feature. If the REST is back compatible for multiple releases that will be fine. The issue is that if we upgrade we will then NOT work with older versions.