hi sathya,
union.xml's client_timeout setting is intended to detect network failures only, and therefore does not affect clients that successfully send heartbeats/pings on a regular basis.
Union does not currently have an application-level activity timeout detection built-in, but it's on the roadmap:
http://factory.user1.net/issues/show/689For now, you will have to implement application-level activity detection yourself. Here is the recommended implementation:
1) on a regular interval, have every connected client send a module message to the server called ACTIVITY
2) when the server receives an ACTIVITY message from a client, it should assign the current time to a server-only, non-shared attribute named lastActive on the client
3) on a regular interval, the server-side module should loop over all connected clients, check which clients have not sent an ACTIVITY message recently, and disconnect them
alternatively, if you want to do the inactivity detection all client side, you could write some actionscript code to monitor user activity, and automatically disconnect the client (reactor.disconnect()) after receiving no inputs for a certain period.
colin