The issue of timeouts is complex in a client/server environment. This complicates, and even impedes, the server's ability to recognize that the user has abandoned the session(s). Because the user may be working with applications that rely solely on the client, long periods of time may elapse that the server would traditionally have counted against the user's time-out. However, such monitoring has little meaning for GUI applications. This facet must also be addressed when training users who will be accessing VISTA via workstations.
The Broker itself does not implement any timeout mechanisms in a traditional VISTA sense. However, a Broker connection will timeout after ten hours of inactivity at which point the server job will terminate. Ten hours was chosen not for security reasons, but rather to clean up servers from abandoned applications.