hook.io

 __    __    ______     ______    __  ___         __    ______   
|  |  |  |  /  __  \   /  __  \  |  |/  /        |  |  /  __  \  
|  |__|  | |  |  |  | |  |  |  | |  '  /         |  | |  |  |  | 
|   __   | |  |  |  | |  |  |  | |    <          |  | |  |  |  | 
|  |  |  | |  `--'  | |  `--'  | |  .  \    __   |  | |  `--'  | 
|__|  |__|  \______/   \______/  |__|\__\  (__)  |__|  \______/  

a way to enable i/o for your node.js application

v0.8.0

hook.io is a distributed EventEmitter built on node.js. In addition to providing a minimalistic event framework, hook.io also provides a rich network of hook libraries for managing all sorts of input and output.

"hooks" provide a very simple and light way to extend an application to seamlessly communicate with other "hook" enabled devices. By design, extending legacy applications to communicate with hook.io is very easy.

hook.io applications are usually built by combining together several smaller "hooks" to compose new functionality in a distributed and organized way.

Features :

• Build large, decoupled, distributed, and fault tolerant I/O heavy applications in node.js
• Create hooks on ANY device that supports JavaScript (cross-browser support via socket.io)
• Spawning and Daemonizing of processes handled with Forever
• Messaging API inherits and mimics Node's native EventEmitter API (with the help of EventEmitter2)
• Interprocess Message Publishing and Subscribing done through EventEmitter2 and dnode
• Easily scale any tcp based messaging infrastructure (such as clustering socket.io chat rooms in memory)
• Easily connect / disconnect hooks "hot" without affecting other services

Additional Resources

• Email List: http://groups.google.com/group/hookio
• Video Lessons: http://youtube.com/maraksquires ( mirror )
• Wiki Pages https://github.com/hookio/hook.io/wiki/_pages
• hook.io for dummies
• Distribute Node.js Apps with hook.io:
• #nodejitsu on irc.freenode.net

Installation

 [sudo] npm install hook.io -g
 

Start a hook

hookio

auto-discovery will now create a hook server if this is your only running hook

Connect another hook

hookio

you now have two hooks connected to each other

This is the most minimal hook.io application you can have. It does nothing. No cruft, no extra baggage.

Connect another hook! With a REPL!

hookio --repl

you now have three hooks connected to each other

Extending your hook.io mesh

At this point, you've got 3 nodes talking to each other, and an interactive repl to run hook.emit and hook.on commands. Now you can extend your network of hooks using any of the existing hook libraries, or by extending from the base Hook object. You can now fire messages cross-process, cross-platform, and cross-browser.

Available Hooks (more coming soon)

Hook Library wiki: https://github.com/hookio/hook.io/wiki/Hook.io-Libraries

You can also search http://search.npmjs.org/ for "hook.io" ( although there are so many matches already, the search interface can't display them all.. )

• cron: Adds and removes jobs that emit hook.io events on a schedule
• couch: Emit hook.io events based on your CouchDB _changes feed
• irc: Full IRC bindings
• helloworld
• logger: Multi-transport Logger (Console, File, Redis, Mongo, Loggly)
• hook.js: Build web apps / use hook.io in any browser
• mailer: Sends emails
• sitemonitor: A low level Hook for monitoring web-sites.
• request: Simple wrapper for http://github.com/mikeal/request
• twilio: Make calls and send SMS through Twilio
• twitter: Wrapper to Twitter API
• webhook: Emits received HTTP requests as hook.io events (with optional JSON-RPC 1.0 Support)
• wget: Downloads files using HTTP. Based on the http-get module by Stefan Rusu
• tar: A hook to wrap around tar
• gzbz2: A hook for compressing and uncompressing files
• mock: A hook that mocks messages. Useful for hook.io related development.

Using hook.io programmatically

Note: This is only one, small, example.

see examples folder for extensive example code

to see all other supported types of hook messaging ( including EventEmitter and Callback style ), see: https://github.com/hookio/hook.io/tree/master/examples/messaging

var Hook = require('hook.io').Hook;

var hookA = new Hook({
  name: "a"
});

hookA.on('*::sup', function(data){
  // outputs b::sup::dog
  console.log(this.event + ' ' + data);
});

// Hook.start defaults to localhost
// it can accept dnode constructor options ( for remote connections )
// these hooks can be started on diffirent machines / networks / devices
hookA.start();

var hookB = new Hook({
  name: "b"
});

hookB.on('hook::ready', function(){
  hookB.emit('sup', 'dog');
});

hookB.start();

Tests

All tests are written with vows and require that you link hook.io to itself:

  $ cd /path/to/hook.io
  $ [sudo] npm link
  $ [sudo] npm link hook.io
  $ npm test

Core Contributors ( https://github.com/hookio/hook.io/contributors )

• Marak (Marak Squires)
• indexzero (Charlie Robbins)
• jamesonjlee (Jameson)
• AvianFlu (Charlie McConnell)
• jesusabdullah (Joshua Holbrook)
• temsa
• mmalecki (Maciej Małecki)
• pkumar (Pavan Kumar Sunkara)
• Marsup (Nicolas Morel)
• mklabs (Mickael Daniel)
• Tim-Smart (Tim)
• stolsma (Sander Tolsma)
• ejeklint (Per Ejeklint)
• thejh (Jann Horn)
• perezd (Derek Perez)
• mwawrusch (Martin Wawrusch)

MIT License

Copyright (c) Nodejitsu

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.