On 28/03/13 15:38, David M. Lloyd wrote:
On 03/28/2013 09:46 AM, Rémy Maucherat wrote:
> On 03/28/2013 03:32 PM, Jason Greene wrote:
>> Hmm not sure I follow. We are talking about the implementation of our ejb client
library (or any other existing remoting client). How it communicates to the server (via
upgrade, web sockets, socket, etc) is just an implementation detail of the client/server
implementation. The user isn't exposed to those APIs to do it.
> Yes, I know it is about the remoting component (and it's the same for
> websockets as well - the user uses the websocket JSR, not the API used
> for the implementation). But you can still choose between proprietary or
> Servlet 3.1 for the implementation since they are supposed to be able to
> do the same thing.
One of Undertow's specific capabilities is to upgrade a connection
directly into a raw XNIO connection with very low (basically no)
overhead, which Remoting can consume directly. Also, the Undertow
implementation is simper and faster by quite a lot. Finally, Servlet
may not always be available.
In the case of domain management it isn't available.