Hi Andrew, 1. As Provider implementation I meant creating the provider's metadata and provider specific API classes, as Ignasi pointed in a previous mail. By the way, maybe i should be clearer on that point.
2. Yes, that's a great idea, thanks for pointing it out. I wrote about it on the list of deliverable results but i should explain it as part of the project planning. 3. I was wondering about the same too. I don't know yet if it will really fit the Blobstore View, because it takes literally hours to read a file. It's not a common storage service and their use cases will be different from the use cases for common storage services. Thanks for the suggestions, your help is really appreciated! Regards 2014-03-17 20:39 GMT+01:00 Andrew Phillips <[email protected]>: > Hi Roman > > Thanks for putting this together! A couple of initial questions: > > * > 5. Provider Implementation > > If I understand the planned iterations before that, you will *already* be > implementing the provider. Is this supposed to be "finish provider > implementation", or are you thinking of something else here? > > * You may want to mention the creation of an working example in the > jclouds-examples repo [1] as part of the documentation effort > > * Would you be intending to try to make the Glacier API support one of the > abstract views (BlobStore, probably?), or keep it as an API and a provider? > > Hope those questions make some kind of sense! > > Regards > > ap > > [1] https://github.com/jclouds/jclouds-examples >
