Hi, This is the discussion group for protocol buffers itself, not any particular RPC system based on them. It looks like protobuf-socket-rpc has its own discussion group which may be the right place for your question.
Incidentally, what you described is fully supported in an RPC system I'm (occasionally) working on in my spare time: http://capnproto.googlecode.com However, it's still in the pretty early stages of development. On Sun, Jan 24, 2010 at 9:10 AM, Adam Fisk <a...@littleshoot.org> wrote: > Is there any way to make protocol buffers bi-directional? I'm very > excited about the addition of persistent connections: > > http://code.google.com/p/protobuf-socket-rpc/issues/detail?id=5 > > The killer additional feature, though, would be if the server could > also send a message to the client at any time, with the client > implementing its own interface. That's not supported in any way right? > This would be particularly useful for creating signaling protocols, a > la SIP and XMPP. > > Thanks. > > -Adam > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to proto...@googlegroups.com. > To unsubscribe from this group, send email to > protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
