thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From George Chung <geo...@glympse.com>
Subject Re: Server to client push RPC
Date Wed, 20 Mar 2013 19:42:53 GMT
Ah, yes. The hanging GET approach.

On Wed, Mar 20, 2013 at 12:15 PM, Ben Craig <ben.craig@ni.com> wrote:

> 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 <yannart@gmail.com>
> To:     user@thrift.apache.org,
> 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" <george@glympse.com> 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 <yannart@gmail.com> 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
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message