I wrote up an example using the Pinboard API from Node: this is written with the idea that I might combine it with other external services (dropbox, facebook, etc).<\/p>\n
The ideal situation here is to iterate over recently bookmarked posts, then call some function on each unseen result (external API, log to screen, etc), like so:<\/p>\n
\nget_posts(pinboard_api, 'recent', pinboard_user_data)\n .then( \n (data) => {\n async.map(data, do_something)\n }\n ).error(\n err\n )\n<\/pre>\nThis ended up being a pretty fascinating trip down the vast list of node modules, and I ended up with this:<\/p>\n
\nlet _ = require('lodash'), \n request = require('request'),\n Promise = require('bluebird'),\n rp = require('request-promise'),\n xml2js = require('xml2js'),\n async = require('async');\n<\/pre>\nlodash<\/b> is a nice functional programming library – great utility belt API for working on collections
\nbluebird<\/b> is a promise library. I don’t really like promises, but they do let you flatten some of the nesting that shows up in Node callbacks. There is another library, “Q”, that seems to be more popular, but Bluebird promises better error handling.
\nrequest<\/b> seems to be the most popular way to do curl\/ajax\/wget style calls
\nrequest-promise<\/b> lets you use HTTP request results as promises
\nxml2js<\/b> lets you parse XML text into JS objects (Pinboard returns XML)
\nasync<\/b> is a library like lodash, but lets you turn the “map” type functions into parallel loops<\/p>\n
Next, I’ve defined some structure about the API, thinking I might want to support other APIs. Here are the important facts about this one:<\/p>\n
\nlet pinboard_api = {\n 'auth': 'auth_token',\n 'recent': {\n returns: [\"href\",\"time\",\"description\",\"extended\",\"tag\",\"hash\",\"shared\"],\n url: 'https:\/\/api.pinboard.in\/v1\/posts\/recent',\n unique_key: 'hash',\n implicit_keys: {\n count: 100\n },\n iter: (result) => result.posts.post \n }\n}\n<\/pre>\nAuthentication is usually the trickiest bit with these integrations (aside from SSL). Pinboard just takes a single authentication token, on your account:<\/p>\n
\nlet pinboard_user_data = {\n 'auth_token': '-------------',\n}\n<\/pre>\nNow, to actually do the work we can combine all this together. Conceptually it’s really simple but complexified a bit by my attempts to leave room to support asynchronous operations + other endpoints and APIs (note I haven’t implemented hiding things that have been seen recently – imagine that is a lookup elsewhere).<\/p>\n
\nfunction post_fields(api, method, user_data) {\n let qs = {};\n qs[api.auth] = user_data[api.auth]; \n _.extend(qs, api[method].implicit_keys);\n \n let options = {\n uri: api[method].url,\n qs: qs,\n headers: {\n 'User-Agent': 'Request-Promise'\n } \n };\n \n return new Promise(\n (resolve, reject) => {\n rp(options)\n .then(\n (resp) => {\n xml2js.parseString(resp, \n (err, result) => {\n if (!result) {\n reject(err); \n } \n \n resolve(\n _(api[method].iter(result))\n .filter(\n (entry) => !seen(entry)\n )\n .map(\n (entry) => {\n markSeen(entry.$)\n \n return entry.$;\n } \n ).value()\n )\n });\n }\n )\n .error(reject) \n } \n );\n}\n<\/pre>\n","protected":false},"excerpt":{"rendered":"I wrote up an example using the Pinboard API from Node: this is written with the idea that I might combine it with other external services (dropbox, facebook, etc). The ideal situation here is to iterate over recently bookmarked posts, then call some function on each unseen result (external API, log to screen, etc), like … <\/p>\n