Thinking with Nodejs Portals
Last Monday was a bank holiday here in the UK, and while most people were playing computer games or out socialising, our CTO, Richard, was starting to truly think with portals. After releasing a ruby wrapper for the Pachube TCP stream API, Richard decided to build a Node.js streaming TCP client for Pachube's TCP server.
Node.js is an event-driven I/O framework for server-side JavaScript, but what does this mean and what does it allow us to do? Well, it essentially allows us to open up portals between events, allowing us to listen for information, rather than asking for it via the web:
Combining this with the Pachube TCP stream API enables us to extend this to real-world devices, creating portals for data to stream through to our software. What are we doing with these portals and this data?...You'll just have to wait and see ;-)
We have of course released the code for this client via the Carbon Calculated Github account; feel free to fork, commit or comment.
