Storage Service Redesign

Two main problems:

• The StorageService implementation has gotten complicated, in part due to bufferized/non-bufferized. Furthermore, others (Jesse, Julien) who have been implemented non-simple storage services have encountered difficulties.

• The static/non-static stuff is getting out of control XRootD stuff + Compound Storage Service stuff + File Proxy is likely duplicating code Abstractions are all over the place. Some SS perhaps shouldn't support paths. Some shouldn't really have file systems and mount points (like Compound). Some don't support paths (like FileServiceProxy).

Thoughts on how to fix it:

We need to think of what functionality the different storage services should provide:

• Which support paths?
• Is the same FileLocation abstraction really applicable to all? (FileServiceProxy is already overriding it, perhaps they should all override it?)
• It makes no sense for StorageService to declare the file systems
• Do they all provide all "meta" operations?

** Tons of small problems/questions **

• Should BUFFER_SIZE be a StorageServiceProperty? what about CACHING_BEHAVIOR???