You should probably be watching Flatiron

[Marak Squires]

To all -

I've been pulling out a lot of the core event map features of hook.io into separate modules under the Flatiron project.

I'll be starting up the new 0.9.x branch of hook.io sometime soon and will be taking several Flatiron projects as dependencies.

New approach will be phasing out event maps in favor of resourceful resources, which can be reflected to various i/o sources using Flatiron.

These are all good changes. We should see significant improvements in functionality and general architecture of hook.io

Good place to start:

http://github.com/flatiron/resourceful

http://github.com/flatiron/restful

http://github.com/flatiron/socketful

[Adam Crabtree]

Care to expand more on this?

"New approach will be phasing out event maps in favor of resourceful resources, which can be reflected to various i/o sources using Flatiron."

Moving away from EventEmitter to a more RPC-style API?

Cheers,
Adam Crabtree

[Marak Squires]

No and no. Follow the repos and figure it out, or wait until blog posts / new version.

[Adam Crabtree]

Lol. Nice. Sounds good. 

Sent from my iPhone

[Marak Squires]

Here is a detailed explanation with working code snippets and a video.

http://blog.nodejitsu.com/resource-reflection-in-flatiron

Cheers!

[Adam Crabtree]

That's pretty sweet. So would hook.io then be a resourceful reflection, with custom routes / events(?) overwritten similar to the restful custom route example?

[Marak Squires]

Something like that. All hooks are going to be converted into resources ( decoupled from any interface )

These resources can then be exposed over any interface and re-used in a non-hook.io application.