Hello
The Wildfly Client libraries (EJB client, Naming client and Transaction
client) are used to allow applications to remotely access deployments on
Wildfly server instances. The EJB client, Naming client and Transaction
client libraries include support these activities over a JBoss Remoting
transport protocol. The Wildfly HTTP client library adds in support for
these activities over the HTTP protocol. The changes described below
apply to the Wildfly HTTP client.
In order to add new features to the Wildfly HTTP client, we require the
ability to version client-side and server-side request and response
handlers, as the use of clients and servers from different Wildfly
versions is supported (see EAP interoperability
<
https://access.redhat.com/solutions/6985239>). Additionally, in order
to allow clients and servers of differing versions to interoperate, we
require a handshake protocol to establish an agreed version of the
client and server side handlers to use during their interactions.
This scope of this issue is to implement a client-side and server-side
handler mechanism and to adjust the existing handshake protocol (EE
interoperability handshake).
For more information on this issue:, as well as the relevant process
issues see the analysis document
<
https://github.com/wildfly/wildfly-proposals/pull/742>.
We have the key players for a feature team for a "community" stability
level feature team on hand (component lead, developer, SMEs), but if you
are interested in this topic please don't hesitate to get involved. We
always welcome additional perspectives and contributions!
Richard