in reply to Re: is my api wrapper abstraction ok (is it perlish?)
in thread is my api wrapper abstraction ok (is it perlish?)

Thanks for your reply. I see. Yours is an interesting abstraction.

Also, there are urls like this: "/answers/{ids}/comments" where it returns comments on the answers returned by ids. So then I'd have to introduce another parameter or type for it.

  • Comment on Re^2: is my api wrapper abstraction ok (is it perlish?)

Replies are listed 'Best First'.
Re^3: is my api wrapper abstraction ok (is it perlish?)
by Arunbear (Prior) on Jan 20, 2013 at 12:30 UTC
    Also, there are urls like this: "/answers/{ids}/comments" ...
    But isn't that the same as the first example above that returns
    http://api.stackexchange.com/answers/123;134;145/comments?sort=votes;o +rder=desc
    minus the query parameters? The code example I gave already handles that case.