Hi all, Regarding the last sentence, I tend to agree, especially for the OCCI: we have a good, consistent and simple API, but it should not be only paper. As SOAP or xmlrpc, OCCI should have its "plug & dev" libraries/framework for building OCCI compliant APIs and extending them. My 2c Jean Le lundi 07 avril 2014 à 15:26 +0000, Sill, Alan a écrit :
OCCI folks,
I ran into the following paper, also presented as a talk at WS-REST this weekend, and thought you might like to see it. I'd be interested in your response!
Paper: Pragmatic Hypermedia: Creating a Generic, Self-Inflating API Client for Production Use by Pete Gamache, Localytics, Inc. Boston, Massachusetts, USA
http://petegamache.com/wsrest2014-gamache.pdf
Talk: Better Laziness Though Hypermedia
http://petegamache.com/wsrest2014-gamache-slides.pdf
In general, I heard a thread running through the conference of "%$^&*() the API; we just want good libraries." I thought that was a bit disturbing and short-sighted, but understandable, and perhaps could be cured by a better design pattern. Hypermedia seems to be one [possible contributor to better design. Thoughts?
Cheers, Alan
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
-- Jean Parpaillon Open Source Consultant Phone: +33 6 30 10 92 86 im: jean.parpaillon@gmail.com skype: jean.parpaillon linkedin: http://www.linkedin.com/in/jeanparpaillon/en