I tried a server implementations like this:

import msgpackrpc

class TestServer(object):
    def Add(self, a, b):
        print("Add({}, {}) called".format(a, b))
        return a + b

    def Mul(self, a, b):
        print("Mul({}, {}) called".format(a, b))
        return a * b

server = msgpackrpc.Server(TestServer())
server.listen(msgpackrpc.Address("localhost", 8070))
server.start()

The client looked like this:

    public partial class Form1 : Form
    {
        private RpcClientConfiguration _clientConfig = new RpcClientConfiguration();
        private dynamic _rpcProxy;

        public Form1()
        {
            InitializeComponent();
            _rpcProxy = new DynamicRpcProxy(new DnsEndPoint("127.0.0.1", 8070), _clientConfig);
        }

        ~Form1()
        {
            _rpcProxy.Dispose();
        }

        private void btnAdd_Click(object sender, EventArgs e)
        {
            for (int i = 0; i < 50; ++i)
            {
                var result = (int) _rpcProxy.Add(Convert.ToInt32(i), Convert.ToInt32(tbB.Text));
                lblResult.Text = String.Format("Result: {0}", result);
                Thread.Sleep(100);
            }
        }

        private void btnMul_Click(object sender, EventArgs e)
        {
            var result = (float)_rpcProxy.Mul(Convert.ToSingle(tbA.Text), Convert.ToSingle(tbB.Text));
            lblResult.Text = String.Format("Result: {0}", result);
        }
    }

(I also tried a C++ server implementation but I'll omit that for brevity; I had the same results with it.)

What happens is after the 10th or so call the application hangs. It always hangs on this line: https://github.com/yfakariya/msgpack-rpc-cli/blob/master/src/MsgPack.Rpc.Client/Rpc/Client/AsyncResult.cs#L224

I does not matter how much I wait between the calls, it can even be as long as two seconds per call.
Am I doing something wrong with the client or is this a bug?

Hello. Me and my colleague are trying to use your msgpack-rpc-cli implementation in C#, however we are having difficulties understanding how we can create a service that the server can provide to the client.

We tried following your Quick Start instructions, but we are still having some difficulties.

So we would like to ask you if you can provide a simple example that we can run and test on Visual Studio. We believe if we have an example with a client and server interacting we can build our application from that.

Thank you for your time, best regards.

I am trying to call an RPC function bar() that returns a value of type Foo. Foo is an identical class on both the server and client.

The dynamic proxy always returns a MessagePackObject, and it's possible to dynamically cast this to a basic type (i.e. ulong). But a compile-time error results if I try to cast it to Foo.

I understand that a serializer for Foo can be created and registered in the SerializationContext, but this doesn't change the fact that I can't perform a cast upon the MessagePackObject returned by the call.

Is it possible to convert the return value to Foo? If it is, could someone please provide a simple example?

I am trying to expose the methods of my server implementation, but it is not working. I don't really know what I am missing.

This is my question opened on StackOverflow, I would appreciate a lot some help.

Thank you very much!!

http://stackoverflow.com/questions/34729557/messagepack-rpc-c-sharp-server-side

Even I change the msgpack-cli ref to 4.0 version, it seem not build successful.

the error : Error CS1061: 'MsgPack.Unpacker' does not contain a definition for 'TryRead' and no extension method 'TryRead' accepting a first argument of type 'MsgPack.Unpacker' could be found (are you missing a using directive or an assembly reference?) (CS1061) (MsgPack.Rpc.Mono)

And It also tips : Serialization not in MsgPack namespaces.

Hi,

is it possible to use this framework but not use the default MsgPack object serialization?
I use the MsgPack c# bindings but use for all objects a customer serializer. But when I use the DynamicProxy for example, the framework would use the default MsgPack serialization.

So there some API to pass byte[] and only take advantage of the communication features?

Thanks!