nom install does not work
It seems package.json has some problem.

Valid install targets:
npm ERR! ["0.1.1","0.1.2","0.1.4","0.1.5","0.1.6","0.2.0","0.2.1"]

It seems to me that there is a bug in the RPC call/result sync. The problem occurs when two (or more) calls are made to the library on very short interval and the server code does something asynchronously, then the returning callbacks are all returning a value to the last call send to Wamp.io.

Here is an example code with my added debug prints.

handlers[protocol.TYPE_ID_CALL] = function(client, args) {
  callId = args.shift();
  console.log("Call id: "+ callId);
  prefixes.resolveOrPass(procUri = args.shift());
  args = args || [];

  // Callback function
  cb = function(err, result) {
    var msg;
    console.log("Result id: "+ callId);
    if (err) {
      msg = [protocol.TYPE_ID_CALL_ERROR, callId, 'http://autobahn.tavendo.de/error#generic', err.toString()];
    } else {
      msg = [protocol.TYPE_ID_CALL_RESULT, callId, result];
    }
    client.send(JSON.stringify(msg));
  };

  this.emit('call', procUri, args, cb);
};

My client code sends two rpc calls and here are the debug prints.
Call id: 0.e1elbygmbg6fajor
Call id: 0.86y08973bkervn29
Result id: 0.86y08973bkervn29
Result id: 0.86y08973bkervn29

So the problem to me seems to be that the scope of the callId variable is local and that is changed whenever a new call is done. I will investigate more to find out a possible solution..

Trying to connect client.js example to a non running server do a Node.js crash. How can I handle connection problems? WebSocket object has an "On Error" event but can't see how to handle using publics Client or Session objects. By now my solutions is to hack Client code and add

 ws.on('error', function(error) {...})

to constructor. Is there a cleaner solution?

Thanks.

When (in examples/pubsub/server.js)

51    app.publish(topicUri, event);

is being called, it seems the following codes could not be initialised,

(lib/server.js)

function Server(options) {
  this.options = options || {};
  this.topics = {};
  this.clients = {};
}

because, at line 108
(lib/server.js)

if (this.topics[topicUri]) 

where this is still empty:

Thus, the if condition is always false.

Is there any instruction how to use server.js in lib/server.js?

If request is wrong: invalid json or invalid wamp protocol server silently ignore request. Is this a bug or maybe this is a protocol specification problem?

The docs say it supports pub/sub, but doesn't give any examples of how to do it... How would the server publish or subscribe?

Probably you would not use WebSocket.IO in your code? and it has switched to WS?

and by the way, there are some things that confused me:

1. in lib/server.js

115 this.clients[id].send(msg);

where is the send from? my IDE shows me from express or jQuery, but you haven't used any of those
2. how do use the debug in your code?

I've a use case where after a CALL server know that this client want to SUBSCRIBE to a event channel, so is unnecessary that client send a SUBSCRIBE msg. How can I resolve that?
Many thanks.

Is there any solutions to take care of timeout of RPC requests?

When it happen:

I opened two clients in different windows on Safari. One sent a message and the other could received, but if either of the clients quit, such as by close the window, it would trigger an error on the server.

What is the output:

The Node.js output says:

wamp.io/lib/server.js:90
      delete self.topics[topic][client.id];
                                      ^
TypeError: Cannot convert null to object
    at WebSocket.Server.onConnection (/Users/Ken/Documents/Projects/wamp.io/lib/server.js:90:39)
    at WebSocket.EventEmitter.emit (events.js:123:20)
    at WebSocket.cleanupWebsocketResources (/Users/Ken/Documents/Projects/wamp.io/node_modules/ws/lib/WebSocket.js:649:23)
    at Socket.EventEmitter.emit (events.js:90:17)
    at TCP.onread (net.js:417:51)

What I thought:

If added one line before the delete self.topics[topic][client.id];

console.log(self.topics[0]);

it outputs undefined, moreover.

the self.topics looks like an object rather than an array, e.g.:

{ 'event:firstevent': { '585972943854826': true } }

Right now this is required to install the package:

{
    "dependencies": {
        "wamp.io": "git+https://github.com/nicokaiser/wamp.io"
    }
}

This should probably be documented in the README, or you could just release a package in the npm registry.

I am not sure if I understand correctly, it seems your server only accept PUBLISH and the format is a bit different from WAMP specification? http://wamp.ws/spec#publish_message

It says: publish (a) message with 'string' as payload [7, "http://example.com/simple", "Hello, world!"]

While your code:
try {
var parsed = qs.parse(buffer);
console.log(parsed);
topicUri = parsed.topicuri;
event = JSON.parse(parsed.body);
}

It seems you need "topicuri" and "body", but the server does not accept: {"topicuri":"http://example.com/simple","body":"something"} or topicuri=http://example.com/simple&body=something
(based on https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/JSON/parse, it should accept body=something)

While it will accept: topicuri=http://example.com/simple&body={"event":"helleo"}
(and this way is different from the specification, maybe?)

As the client side library, Autobahn.js have problems on connecting your example server. Thus, I tried the following comparison,
The first one will connect to Autobahn.js testing WAMP server, by running command:
more here: http://autobahn.ws/js/getstarted

wstest -d -m wampserver -w ws://localhost:9000

Then, in Chrome console, I run:

var ws = new WebSocket("ws://localhost:9000",["wamp"])

then the ws will be initialised:

WebSocket {binaryType: "blob", extensions: "", protocol: "wamp", onclose: null, onerror: null…}

_As you can see that the protocol contains "wamp"_

So I did the same thing on your example server (wamp.io/examples /pubsub/server.js)
either
corresponding to

15 var ws = wsio.listen(9000);

var ws = new WebSocket("ws://localhost:9000",["wamp"])

or
corresponding to

61 api.listen(9090);

var ws = new WebSocket("ws://localhost:9090",["wamp"])

but the different is the ws giving no protocol:

WebSocket {binaryType: "blob", extensions: "", protocol: "", onclose: null, onerror: null…}

I also tried mine on top of express, which I asked you days ago,

...
var app = express();
var server = http.createServer(app);
var wamp = wampio.attach(wsio.attach(server));
app.configure(function(){
    app.set('port', process.env.PORT || 3000);
    ...
}
...
server.listen(app.get('port'), function(){
    console.log("Express server listening on port " + app.get('port'));
});

var ws_1 = new WebSocket("ws://localhost:3000",["wamp"])

but it returns the same ws without protocol.

I think this might be the reason that AutoBahn.js cannot contact to. What do you think?

(In the image, I changed your port to 8000 rather than 9000)

Is there any support planned for https://github.com/sockjs/sockjs-node?

I believe (perhaps you can correct me on this) the only abstraction that is missing is the name of the command to send on the socket (currently .send, SockJS uses .write) and the event name for incoming data (currently "message", SockJS uses "data"). I made the change to test it and it works correctly (validated using AutobahnJS through SockJS-client on the client side), but perhaps there are some internals I'm not aware about that could break in some cases.

sockjs/sockjs-node#67 is a related discussion where it was decided SockJS would not rename the call to .send and the event name to "message".

I was wondering, why is ws currently a dev dependency (and not a dependency altogether) in the package.json? I cannot use the wamp.io module if it doesn't have ws installed.

Thank you.

It seems there is something not work with the WAMP specification, in lib/handlers.js (but I am not sure whether my understanding is correct or not)

38 handlers[protocol.TYPE_ID_CALL] = function(client, args) {
39  callId = args.shift();
40  prefixes.resolveOrPass(procUri = args.shift());
41  args = args || [];
  ...
55  this.emit('call', procUri, args, cb);
56};

After line 41, the args will turn to an array like Object, meaning the args looks like an array, but the type of it is an Object.
e.g. the RPC message argument in [2,"4qK7nmQUsumUSGUM","calc:sum",[1,2,3,4,5]] is [1,2,3,4,5], but after your code line 41, it then changed to [ [ 1, 2, 3, 4, 5 ] ]

For more information, please check this screen shot.