It's somewhat problematic having a max session timeout as the running time of any session is all over the board. Now, there is an implied session lifetime that is enforced (though it can be configured away). From the client's perspective if a connection becomes idle it is closed thus ending the session. From the server's perspective if idle timeout is enabled and the connection goes idle the connection is closed ending the session. One could argue that any session that is active should be allowed to live for a relatively long time. However, I don't see how we can all agree on the definition of "long".


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1784/1254606331@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1784#issuecomment-1254606331", "url": "https://github.com/xrootd/xrootd/issues/1784#issuecomment-1254606331", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1