[ http://jira.jboss.com/jira/browse/JBREM-45?page=all ] David Lloyd closed JBREM-45. ---------------------------- Resolution: Out of Date Assignee: David Lloyd (was: Tom Elrod) This issue is in three parts: 1) Build in ability for the server to be aware of clients that exist and their status. Remoting 3 does not have a notion of client vs. server. That said, an Endpoint will always be aware of the status of its Sessions. 2) Add distributed garbage collection for clients that maintain a remote stub. Will detect that client is no longer available (via watchdog) and will clean up server side references. This is probably out of scope for Remoting 3 - I'm inclined to let this die until a specific issue arises. Specifically, Remoting 3 doesn't normally utilize the idea of a remote object. Anything that does, will be built on top of Remoting 3 and will probably be responsible for dealing with this functionality. 3) Need ability to disconnect client from server when there has been an extended period of inactivity. This would be very specific to the protocol. Additionally complicated by the addition of Context/Session layers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira