As for the method name, what would you have chosen? It's a generic official name "Product Advertising API", not a lot of room there. I guess leaving off the create wouldn't heart, productAdvertisingClient() is pretty verbose, but productAdvClient() not so bad.
Re:Node.js library for the Amazon Web Services
by jfarmer on Thursday January 19, 2012 @03:37PM
(#3486564)
I would rather have something verbose that corresponds to the underlying API than something I have to guess or remember.
Is it createProdAdvClient, createProductAdvClient, createProdAdvertisingClient, createProdAdvertClient, etc.?
Completely arbitrary.
My ideal API clients have a base layer that maps intuitively to the underlying API, and a developer-friendly upper layer with idiomatic method calls.
A common trick in Ruby, for example, is to give the API client a proxy method (e.g., api) that uses method_missing to map method calls to API end points.
You wind up with API clients that look like client.api.some_method(...). Under the hood it might transform some_method into "someMethod" before it makes the API call.
However, if you want, you can still access the raw API endpoints programmatically.
Just my preference, I realize, but I think it's important for libraries to idiomatic.
Re:Node.js library for the Amazon Web Services
by ntkachov on Wednesday January 18, 2012 @02:07PM
(#3481284)
My one issue with this mod (and most amazon mods for node) is that they don't include S3 support AND SimpleDb support.
The node app I'm writing needs S3 and SimpleDB and thats it. But the only library that has that doesn't work with my system. Fortunately i found two separate mods that do what I need really well.
Re:Node.js library for the Amazon Web Services
by rgbrgb on Wednesday January 18, 2012 @02:07PM
(#3481287)
On a related note, if you just want something tiny to interact with s3, check out Knox (https://github.com/LearnBoost/knox). I used it on a recent project and it was very easy with a clean API.
Re:Node.js library for the Amazon Web Services
by adrianparsons on Wednesday January 18, 2012 @01:36PM
(#3481112)
This library is great (and it's been around a while). It even abstracts relatively easy tasks (like product search), making them ridiculously simple to execute.
Edit: Also, didn't notice, but the upper-case key names in the hash passed to the call method are also ugly, IMO.
http://docs.amazonwebservices.com/AWSECommerceService/2011-0...
As for the method name, what would you have chosen? It's a generic official name "Product Advertising API", not a lot of room there. I guess leaving off the create wouldn't heart, productAdvertisingClient() is pretty verbose, but productAdvClient() not so bad.
Is it createProdAdvClient, createProductAdvClient, createProdAdvertisingClient, createProdAdvertClient, etc.?
Completely arbitrary.
My ideal API clients have a base layer that maps intuitively to the underlying API, and a developer-friendly upper layer with idiomatic method calls.
A common trick in Ruby, for example, is to give the API client a proxy method (e.g., api) that uses method_missing to map method calls to API end points.
You wind up with API clients that look like client.api.some_method(...). Under the hood it might transform some_method into "someMethod" before it makes the API call.
However, if you want, you can still access the raw API endpoints programmatically.
Just my preference, I realize, but I think it's important for libraries to idiomatic.