airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saminda Wijeratne <>
Subject Re: Using same Thrift server to host multiple thrift services
Date Wed, 21 May 2014 19:56:50 GMT
Introducing service multiplexing at this stage seems to be a little
problematic since thrift 0.9.1 does not have service multiplexing support
for php clients[1]. The relevant classes[2] were introduced to the thrift
trunk after the 0.9.1. release but after testing using those classes the
php client threw exceptions showing that they probably need more work on
that front.

If we enable the server with service multiplexing then the any client
connecting to that server MUST USE the service multiplexing protocol. Thus
right now only option is to differ using service multiplexing for Airavata
API and start a new thrift server for the new ApplicationCatalog thrift


On Mon, May 19, 2014 at 8:24 AM, Suresh Marru <> wrote:

> Hi Saminda,
> I haven’t put thought on the names yet, but yes thrifty multiplexing
> worked well when I prototyped it on 0.9.1. So + 1 on reusing the same
> server and ports.
> Suresh
> On May 19, 2014, at 11:10 AM, Saminda Wijeratne <>
> wrote:
> $subject is a feature supported from Thrift 0.9.1[1]. With the intro of
> ApplicationCatalog we need to provide this in order to avoid multiple
> thrift servers.
> In order to allow the client to distinguish each service must be uniquely
> named. We have 2 main thrift services for gateways right now.
>     - AiravataAPI
>     - ApplicationCatalog
> For now I'm going to use the same names. However I think its best we
> establish the names properly if we are going to have an API segmented in to
> several more thrift services like this. (eg: at the moment AiravataAPI is
> governed mostly with experiment related functions). Any suggestions?
> Thanks,
> Saminda
> 1.

View raw message