Out of band messages not consumed by correct consumer when multiple consumers about protobuf-rpc-pro

[GoogleCodeExporter]

Thanks for raising this - please no appologies. Do you have any code sample 
which i can use directly to reproduce - this could save me some time when 
looking at it. I will probably have some time this weekend.

Original comment by [email protected] on 19 Sep 2013 at 8:39

[GoogleCodeExporter]

I see the issue is the following : on any RpcClientChannel - it is only 
possible to register a single OobMessageListener instance. See javadoc 
com.googlecode.protobuf.pro.duplex.RpcClientChannel

    /**
     * Allow to register a callback for unsolicited messages from the server.
     * Non correlated messages are messages which are not related to any ongoing RPC
     * call. 
     * 
     * Only a single oobMessageListener is allowed at a time. Setting the responsePrototype 
     * or oobMessageListener parameter to null will "switch off" the onMessage reception within the
     * client. This does not prohibit servers sending uncorrelated messages to a client which
     * wastes bandwidth and ignores the messages.
     * 
     * @param responsePrototype the prototype of the messages which can be handled out-of-band from the server.
     * @param oobMessageListener a callback function when an unsolicited messages is received from the server.
     */
    public void setOobMessageCallback( Message responsePrototype, RpcCallback<? extends Message> oobMessageListener );
}

This should not be a problem, because you can always define a protobuf message 
which contains a choice of several other messages, where each is "optional". It 
just means you need to do the dispatching in your own code.

If you want this feature badly - you can open a Feature request and i could 
make a new release to support multiple OobMessageListeners and do dispatching 
in the library.

Original comment by [email protected] on 21 Sep 2013 at 2:39

• Changed state: WontFix

[GoogleCodeExporter]

Sorry for the late reply.

No worries about the multiple OobMessageListener, I took your advice and am 
using the common message with several option messages.  Everything is working 
well now.

Thanks

Original comment by [email protected] on 26 Oct 2013 at 2:41