API wrapper best practices?
davehodg at gmail.com
Sat Mar 23 16:36:07 GMT 2013
Really? Got a good example of where this is done and isn't a pain
in the ass?
On 23 Mar 2013, at 16:05, Mike Whitaker <mike at altrion.org> wrote:
> You mean apart from doing all the things you just said you're not going to do?
> On 23 Mar 2013, at 16:01, Dave Hodgkinson <daveh at hodgkinson.org> wrote:
>> So I'm writing an interface to an API. It's a simple info request one.
>> What top tips do we have for writing one that doesn't suck? I'd
>> just go for a new that takes the auth info, methods to go fetch
>> the information and being lazy, just let the data be accessible
>> through the selfish hash.
>> I'm not going to create objects for all the data objects at this point
>> nor accessors for the individual fields. Well, maybe a few key ones.
>> Suggestions for anything better, lazier, more modern?
More information about the london.pm