50 likes | 61 Views
This document highlights the main problems with SRM v2.1 definitions, including default values for missing optional arguments, issues with recursive methods, confusion regarding fileStatuses in RequestToGet and Rmdir, error handling, and more.
E N D
Jean-Philippe Baud CERN/IT/GD Problems with SRM v 2.1 definitions
Main problems (1) • Default values when optional arguments are missing, for example • fileStorageType in PrepareToGet • KeepSpace in ReleaseFiles • What to do if size of array of requests/paths is zero? • Recursive methods • What should be in fileStatuses for RequestToGet, Rmdir: original directory name or individual file names? • What should happen in case of error: best effort or stop at first error?
Major problems (2) • SetPermission • One should be able to set permission for “group_owner” or set default ACLs on directories • Need better definition of • RemoveFiles/AbortFiles/ReleaseFiles • ReleaseSpace/CompactSpace • Role of ReleaseSpace force: releasing a permanent file ??? • Ls vs GetFileMetaData
More detailed problems (1) • Written document does not match WSDL • Different names • Different types: long vs unsigned long for TSizeInBytes • isExtended flag is in doc but not in WSDL • Why specifying push/pull mode for PrepareToPut/PrepareToGet if remote access is not supported? • Meaning of isValid in TMetaDataSpace • TPermissionMode null in SetPermission read ?? • Ls method: lifetimeleft is normally associated with a request??
More detailed problems (2) • ExtendFileLifeTime: why returning 0 and not current lifetime if extension refused?