@abh3 That sounds very reasonable to me, it also sounds like a very "lightweight" solution in terms of CPU power and without additional heavy locking. Well thought out.

I am not sure how high the risk is that the reference count never / rarely ever goes to zero (on very busy servers with long-lived connections), that would be the only potential issue I could think about. If that is a real issue, it might be good to echo a warning into the logs if a refresh is long overdue and cannot be made due to the reference count not dropping.

The proposed timescale is also perfectly fine with me (minimal in R4, good solution in R5), but @esindril is probably the more heavy affected one here, so I'll leave that judgement to him.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/750#issuecomment-617493564", "url": "https://github.com/xrootd/xrootd/issues/750#issuecomment-617493564", "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