Remoting 3 is architectually fundamentally different from previous versions. Connections are designed to be long-lived and shared and multiplexed with many protocols across one connection; in addition the API structure is substantially different. Remoting 3 acts in terms of Endpoints. You create an endpoint, register any local services on it, use it to establish authenticated connections to remote endpoints or to create servers for incoming remote connections. You then can use connections to open clients for specific services (for example, EJB, JNDI, and JMX are all separate services in JBoss AS 7 but you can access them all over one connection).
Thus your question doesn't really have meaning in the context of Remoting 3. Hopefully I'll have some time sometime soon to start developing and publishing some good documentation.
Thanks for the responses. I was looking for ConnectionValidator class for getting a notification in my client code when the server side connection drops/goes down for some reason. The client code can after all get a notification if it registers a handler for connection close. The RemoteReadListner class will listen for closed connections and invoke the connection close handler, which will notify the client handler about the connection close. I got it by going through the JBoss AS code. Please let me know if this is the way to go about getting notifications in remoting3.