Print

Print

Whi;le such an approach is doable for simple services, the complex nature of the server makes is unfeasable. Consider that each plugin would have to re-initialize and persistent state may get invalidated and providing consistency across a existing sesssions would be incredibly difficult if not impossible. Instead, we chose to provide recoverability via the client. Restating a server should not fail any existing client as it simply reconnects after a restart and continues where it left off if the new configuration allows it (think, among other issues like changes in security or exports). That has proven to be the most reliable way allow on-the-fly configuration changes.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

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