Creating and Consuming SDKs

mattwhetton commented 8 years ago

A consistent pattern to use when creating an SDK. Should address things like:

Located in separate repo or with API repo
How initialised for usage (should be consistent across all sdks)
Enabling oakbrook headers
Instrumentation (within the sdk, outside the sdk, achieved using decorator
Logging (within the sdk, outside the sdk, achieved using decorator
A typical request / response pattern
How exceptions should be handled (e.g. throwing http exceptions vs returning a response with error details)
RestSharp or HttpClient

wordshaker commented 8 years ago

Mind if I assign myself to this? Would help to solidify my knowledge in this area.

neonboxx commented 7 years ago

Also need to mention how we handle the Conversation Id in relation to SDKs

Sequensis / sequensis.github.io