thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Kinnis <tkin...@yahoo.com>
Subject Re: Multiple interfaces handled by the same TServer
Date Mon, 14 Feb 2011 17:24:48 GMT
This is not exactly what you were looking for but as an alternative you can 
emulate this over HTTP by mapping your different services to URLs. Of course, 
you'll have additional overhead with HTTP but you can support many different 
services on a single server:port. I am currently doing this using Netty as my 
http server and it works very well.


----- Original Message ----
From: Bryan Duxbury <bryan@rapleaf.com>
To: user@thrift.apache.org
Sent: Mon, February 14, 2011 8:25:39 AM
Subject: Re: Multiple interfaces handled by the same TServer

There's currently no clean way to do this. A while back, there were some
proposals on how we could support this directly, but they did not get fully
implemented. I think it was James King and his "channels" proposal that you
might want to look for in the mailing list archive.

On Mon, Feb 14, 2011 at 5:05 AM, Marlene Marques
<marlene.marques@gmail.com>wrote:

> Hi,
>
> Can I have more than one interface being served by the same TServer?
>
> I'm using a TServerSocket and wanted to have more than one interface
> being served in the same port.
> I started to implement a TProcessor that has a processMap with the
> methods of all the interfaces, but now I have a naming collision and
> can no longer use this approach.
>
> To get things going I had a prefix to the operations of each
> interface, but that feels like a really bad hack.
> I also went to change the generated code to have the prefix only in
> the process map and the TMessage, but this is not a better hack, since
> now I can't give my idl to someone to implement a client that works
> with my service.
>
> Thanks,
>
> Marlene
>



      

Mime
View raw message