Support for acknowledgment functions? about go-socket.io HOT 5 CLOSED

What's acknowledgment functions? Is it a part of socket.io? I can't understand your propose.

from go-socket.io.

Sorry for not explaining myself fully. Currently my emit is passing a function as a callback, http://stackoverflow.com/questions/20337832/is-socket-io-emit-callback-appropriate is an example

from go-socket.io.

I'm not good at javascipt. So please point out if I'm wrong.

The example in stack overflow seems pass a callback function from client to server first, then pass back to client from server, and client use that function to do something.

If so, golang doesn't have the capability to marshal the function. It's a compiled function and can't be re-parse to something like code again. It's the main different of compiled language and dynamic language.

from go-socket.io.

You are 100% correct on the intent of the code.

However, Golang doesn't actually have to marshall a function. All it has to do is pass the args, it doesn't care about the contents of the function. I don't know the socket.io protocol, but consider the following.

      socket.emit('fooBar', function(val) {
        //val will be equal to true
      });

    func fooBarHandler(ns *socketio.NameSpace, callback func(val interface{}) interface{}) {
      callback(true)
    }

So we will lose all type safety, but I have no idea how the socket.io protocol works. In my head it looks like the emit is just blocked until it gets a return from the callback. I have no idea though.

from go-socket.io.

Implemented by PR #36

from go-socket.io.