Thanks Ben, That seems to be a better aproach! The only problem I can see is that the server needs to wait that the client send again a new RPC to be able to send a new message, but with a message queue on server should be ok.
Regards, Yann 2013/3/20 Ben Craig <[email protected]> > Open up a second connection to the server, and have the return of that > function be the server->client events. As soon as the client gets the > events from the server, it can start up the call again. > > > > From: Yann Nicolas <[email protected]> > To: [email protected], > Date: 03/20/2013 11:27 AM > Subject: Re: Server to client push RPC > > > > Hi, > > Thanks for your quick reply. I am considering using also the client as a > server but if possible I want to avoid that because of firewall > limitations > and because clients do not have always a host recheable from server. > The is no way to have the server using same socket to respond to RPC and > also invoke to client instead of opening another socket in server to > client > direction? > > Thanks, > > Yann Nicolad > El 20/03/2013 10:09, "George Chung" <[email protected]> escribió: > > > You could always make the client a server as well and support > > bi-directional rpc's. whether this is a viable choice for your specific > > scenario I wouldn't know but it does work. > > > > Sent from my iPhone > > > > On Mar 20, 2013, at 8:12 AM, Yann Nicolas <[email protected]> wrote: > > > > > Hello, > > > > > > I need to do be able to send messages from server to client using the > > > transport created when the client connect to server. This to send push > > > notifications to clients when something changes on server side. > > > > > > My server is C#, my clients are Java & C#. > > > > > > Is there a clean way to do that with Thrift? If not, it is planned in > the > > > future? > > > > > > Thanks, > > > > > > Yann Nicolas > > > >
