 |
 |
Are you saying that the specification is correct, and the same numerical value (`kXR_mkpath`) should be used in both `kXR_mkdir` and `kXR_open` commands? If so, fixing this in SLAC xrootd would require a non-backwards compatible change in SLAC xrootd software. However, this breaking backwards incompatibility is simply not needed. There is no reason the same semantics must be represented by the same numerical value in different operations. The current SLAC xrootd behaviour is perfectly reasonable: using 0x01 in `kXR_mkdir` and 0x100 in `kXR_open` to indicate paths should be created automatically. Therefore, my proposal to fix this (update documentation, changing the `kXR_mkdir` command's constant from `kXR_mkpath` to `kXR_mkdirpath`) will resolve this issue without requiring any changes in SLAC xrootd and without breaking backwards compatibility. This solution treats the problem as a simple typo in the specification. Fixing it is equally easy. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/815#issuecomment-421287642 ######################################################################## 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