JamesHR3 d9e11b21ae Remove targetPlatformVersion check from FinalityFlow and update docs (#4955)
In Corda 4, FinalityFlow was updated to become an initiated flow, in order to ensure a node does not have to accept any signed transaction it receives without being able to check it first. The old behaviour of FinalityFlow was gated behind a targetPlatformVersion check, to prevent apps targeting V4 from using the old behaviour.

This is problematic for a few reasons. For an app wishing to be backwards compatible with a version running on V3, this forces the app to set targetPlatformVersion = 3, even if the app is thoroughly tested against V4. This goes against the purpose of the targetPlatformVersion. Another consequence is that an app remains pinned to targetPlatformVersion = 3 until it is sure that there are no other apps running at a lower version in the network, which would prevent newer versions of the app from taking advantage of features gated behind targetPlatformVersion checks. (Note that the restriction only prevents a new version of the app from initiating FinalityFlow with the old version - the old version is able to initiate a FinalityFlow and the new version will handle it, assuming the app has been written correctly.)

This fix removes the targetPlatformVersion check from FinalityFlow, and also provides a few documentation updates to clarify what level of testing would be expected to set a targetPlatformVersion.
2019-03-28 14:21:59 +00:00
..
2018-05-22 15:38:43 +01:00
2019-03-27 15:25:40 +01:00
2019-03-27 15:25:40 +01:00
2019-03-27 15:25:40 +01:00
2019-01-08 15:52:24 +00:00
2018-07-20 16:21:24 +01:00
2017-09-29 17:42:49 +01:00
2019-03-27 15:25:40 +01:00
2019-03-27 15:25:40 +01:00
2019-03-27 15:25:40 +01:00
2019-01-14 10:07:51 +00:00
2019-01-14 10:55:39 +00:00
2018-11-05 15:51:42 +00:00
2019-03-12 17:25:47 +00:00