 |
 |
@bbockelm I can't say I am thrilled on making the authorization any more complicated than it already is. In practice, people are already confused with all the various levels of authorization. Adding two ore simply is not going to fly all that well for the regular admin folks. Plus, we have been trying very hard to keep dCache and xrootd semantically consistent. This change would undo that and I don't think the dCache folks would be particularly happy introducing these changes as they seem to have very limited benefit (more like authorization gone berserk). However, I am always capable of being convinced otherwise.
As for automatically creating directories, the default xrootd actions is to create such directories for mkdir, open, and even rename. This has been historical and cannot be changed, at least on the xroot side, since people depend on this action. I suppose you can change it on the http side but be aware that you may get howls of defiance and spec be damned as people want paths to be automatically created. So, please don't blindly follow the spec without considering what the practical side effects will be.
As for checking existence using open+EXCL that uis a bad idea as you may leave empty files lying about. Better to use stat().
—
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