I found out that it is highly likely that the current 1.2.5 release will most likely break MGW. While the code changes required are probably minimal, since big money is at stake, if it does turn out not to be backward compatible I will take MGW offline at DGS block.
I suggest that people either protest to make sure the new release is 100% backward compatible, or to withdraw everything from MGW. Either way is fine by me. The latter will allow for clean migration to production servers. The former allows me to not worry about this right now.
I really cannot be keeping up with the daily new releases. Once I finish something, it is nice if I can assume it will continue working without a new release breaking backward compatibility.
Simple syntax changes like "Account" -> "AccountId" seems like no big deal, except it breaks software that is looking for "Account"
why such changes are made is a mystery to me, it has no value and "Account" could have stayed "Account" and not caused breaking of already debugged and working apps.
All of these new encryption modes and features are nice, but when default behavior breaks things then I do not like it. Please find a dedicated MGW dev or make sure NRS releases are backwards compatible. API behavior needs to be stable
James