Puck disconnecting after running function from the browser without passing a callback.

It's that Puck.connect is the more 'advanced' way to talk to the Pucks - I'd been assuming that you would want full control of the input and output if you used it.

As a result, it's a bit harder to give you full control of the IO and then to yank it back when eval needs to be executed and then return it afterwards. It's not that bad though.

If you want to add some extra stuff to it, pull requests are welcome :)