This might affect the RO specification in several aspects, e.g. the tcp-server-list attribute of the /v1/register-application service does no longer fit.
tcp-server-list has to be changed back to single instance while regarding backward compatibility and semantic versioning.
This might include defining a /v2/register-application service at RO first, before changing the ApplicationPattern second.
In ApplicationPattern issue #649 it has been decided to abandon the concept of multiple TcpServers.
This might affect the RO specification in several aspects, e.g. the tcp-server-list attribute of the /v1/register-application service does no longer fit.
tcp-server-list has to be changed back to single instance while regarding backward compatibility and semantic versioning.
This might include defining a /v2/register-application service at RO first, before changing the ApplicationPattern second.