Hello, I have created an initial analysis document for EAP7-1795, EAP7 apps have to communicate with EAP8 apps successfully: [1] This proposal describes proposed changes to various libraries. [1][2][3] and [4] below show proposed changes in detail. Two initial questions to start the discussion: Q1) Is wildfly-proposals/backward-compatibility the right place for that feature? Q2) Is hard requirement no. 4 correct? (Backward compatibility mode is on by default.) The Q2) is related to WildFly Http Client proposed changes only. [1] https://github.com/wildfly/wildfly-proposals/pull/447 [2] https://github.com/ropalka/jboss-marshalling/commit/b9fef744c2eae23600287... [3] https://github.com/ropalka/jboss-ejb-client/commit/327a2d5d286a8405baf0b6... [4] https://github.com/ropalka/wildfly-naming-client/commit/a5b6ae62806ef18a8... [5] https://github.com/ropalka/wildfly-http-client/commit/caa62bdc70cfb6ef174... -- Richard Opalka Principal Software Engineer Red Hat JBoss Middleware Mobile: +420 731 186 942 E-mail: ropalka(a)redhat.com