Hi Amit, > Storage class should be included if it can be, so long as it serves a > purpose. I’m not sure I’m seeing the purpose yet. > > Why I added "storage class" as separate from "priority" was to highlight some DataStore(s) would need special handling for reads/writes for e.g. a read from Glacier may not be immediately available, S3 IA advertises availability as 99.9% and not 99.99% as is the case for S3 (1 in 1000 read request can fail vs 1 in 10000). We would probably need some mechanism to handle/signal the callers by having callbacks/exceptions/logging etc. I am not saying this particular thing is what should be implemented right away though and we cannot cover every nuanced interpretation of categorizing the DataStore(s).
Thanks for the clarification - I think I understand the goal now, and I agree with you at least generally. As I’ve thought about how I might implement an algorithm to look through a number of delegates, it is definitely the case that I would want to know the storage class so I prioritize it appropriately compared to other delegates. I’ll update the wiki. -MR
