I'm in the same situation as Erik, where a would like that my server can send notifications to my client. Can you explain furthermore how to implement the FooRpcController. I'm kind of stuck here and I don't kown how to proceed...
Thx On Wednesday, 9 July 2008 13:07:18 UTC-4, Kenton Varda wrote: > > On Wed, Jul 9, 2008 at 9:57 AM, Erik <[email protected] <javascript:>> > wrote: > >> The only thing I have not found a replacement for are asynchronous >> notifications. Imagine that we are communicating directly over TCP >> sockets instead of over HTTP. Ideally, I would be able to have a >> client make RPC style calls against a server and the server would be >> able to asynchronously push updates to the client using the protocol >> buffer format. I recognize that I can have a client poll for updated >> information, but that is not the direction I'd like to go. > > > This is the kind of thing that could easily be implemented by a particular > RPC implementation, but I did not put it in the base interfaces because I > don't expect all RPC systems to support this. > > Basically, when implementing RPC system Foo, your FooRpcController could > have methods like: > > // client-side > void notifyOnAsyncMessage(protobuf::Message* stream_message, Closure* > done); > > // server-side > void sendAsyncMessage(const protobuf::Message& stream_message); > > You don't get the nice, type-safe interfaces that the rest of the RPC > system provides but it's still pretty easy to use. Also, you would have to > down-cast the RpcController to FooRpcController on the server-side, which > is a bit ugly. What do you think? > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/groups/opt_out.
