 |
 |
This is the third PR in the series (to be reviewed after #1953 and #1954; it'll be rebased on top of whatever those become).
This implements the HTTP max-age directive, allowing the client to control how old the data returned can be. If the cached copy is over the age threshold, either the PFC will delete it (if the file is being opened for the first time) or the HTTP request will (for files that are already opened by other clients).
This will need the most careful feedback from @osschar as it contains a key improvement for the XrdPfc -- an Unlink request no longer invalidates all open file handles but rather the next read will cause it to be reopened.
Note the careful cleanup of the HTTP GET state machine -- now each request state represents a unique operation instead of overloading the request state with other pieces of information. I also tried to add some more careful comments to the state machine to try and make it more understandable by the next developer.
https://github.com/xrootd/xrootd/pull/1957
(15 files)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
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