Back to General Discussion

Should we add an API for modules specific to particular cloud vendors?

Should we add an API for modules specific to particular cloud vendors?

One of the mandates of the project is to keep the API compliant with all cloud vendors. But this can severely limit the functionality available in parts of the API. If we create an extension API, developers will still be aware when they are using a vendor-specific feature.

What would such an API look like?

,Wil

Replies

Adapter Interfaces

Reply by Wil Moore III on Oct 17, 2009

I definitely believe we should implement an adapter interface for vendor specific features. Users wanting to stay "clean" can choose not to pull in the vendor-specific adapters.

Adapter Interface Design?

Reply by Wil Sinclair on Oct 26, 2009

What do you think these adapter interfaces should look like? Maybe interfaces that extend the common interfaces? Providing multiple side-by-side interfaces that are not in the same inheritance hierarchy is another option. But breaking the one-to-one relationship between PHP interfaces and the services may make things more confusing and 'cluttered'.

Adapter Interfaces

Reply by Peter on Nov 4, 2009

Agree, we should have an adapter interface for vendor specific features. I think this will aide in keeping code that uses these features somewhat consistent and aid in interoperability. I think having the new interfaces extend the common interfaces is likely the best option.

Is there anything happening here?

Reply by Jonathan Marston on Mar 30, 2010

Site looks pretty dead, is there any movement since the announcement several months

Add New Reply