ddp.on() is not reacting to "result"-messages

Hi! I'm playing around with ddp.js. I'm trying to build a client that speaks to a meteor server over ddp. But the behaviour i'm seeing is odd. Chances are I'm missing something fundamental.

I have something like this on the client:

var options = {
    endpoint: "ws://localhost:3000/websocket",
    SocketConstructor: WebSocket
};
var ddp = new DDP(options);

ddp.on("connected", function () {
  console.log("Connected");
   var methodId = ddp.method("testMethod");
   ddp.on("result", function (message) {
      console.log(message);
   });
});

testMethod:

Meteor.methods({
    testMethod: function(){
        return "herro";
   }
});

ddp.on("connected") gets triggered as one would expect. However ddp.on("result") does not. When going into the Chrome network console and looking at the DDP-messages being recieved by the client.

{"msg":"result","id":"0","result":"herro"}

But the on() function doesn't react to the event.

Tell me what I'm doing wrong =)

Another example. Here - "added" gets triggered but "ready" does not... Ie. I can subscribe to an meteor collection and when that collection gets updates on the server, an "added" message is sent to the client and the client reacts to it (which is essentially the functionality I need so I'm OK there). I just want to understand how some of this messages triggers the on() function and some don't.

var subId = ddp.sub("qpsYq5zEyFHLwp27b");
    ddp.on("ready", function (message) {
        console.log(message);
});
ddp.on("added", function (message) {
    console.log(message);
});

[michaelstephendavies]

Hi

I had the same problem. Turns out the version of ddp.js in the bower repository is out-of-date, and it passes result, updated and ready differently.

[overcls]

hi,

SocketConstructor: WebSocket
^
ReferenceError: WebSocket is not defined