Print

Print

Correct. The XrootD Xcache assume read-only file. If you want that kind of flexibility then you need to use XcacheH (though only HTTP access is available). This has to to do with semantics. In the XRootD world, caching of files that change makes no sense. That is not true if the HTTP world. So, if you need that kind of flexibility, use XcacheH.

—
You are receiving this because you commented.
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/668#issuecomment-726677600", "url": "https://github.com/xrootd/xrootd/issues/668#issuecomment-726677600", "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