Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <53B54FCA.5010507@iu.edu>
Date: Thu, 03 Jul 2014 08:42:50 -0400
From: Marlon Pierce <marpierc@iu.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: architecture@airavata.apache.org, Airavata Dev <dev@airavata.apache.org>
Subject: Re: Thrift and HTTP
References: <53B4539E.8050306@iu.edu>
 <CAALcEpgBhtyA2800_UV6NunBetFRqhRsraCJDcKG0kU+2uTCrg@mail.gmail.com>
In-Reply-To: 
 <CAALcEpgBhtyA2800_UV6NunBetFRqhRsraCJDcKG0kU+2uTCrg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

All of them.  By public, I don't mean unauthenticated but public in the 
Evernote SDK sense.

Marlon

On 7/2/14, 10:56 PM, Supun Kamburugamuva wrote:
> Hi Marlon,
>
> Could you please give some examples of Airavata APIs that needs to be
> public?
>
> Thanks,
> Supun..
>
>
> On Wed, Jul 2, 2014 at 2:46 PM, Marlon Pierce <marpierc@iu.edu> wrote:
>
>> I'm curious if anyone has looked into running Thrift over HTTP.  We are
>> using TThreadPoolServer for the server and TServerSocket for transport in
>> AiravataAPIServer.java, but we're being encouraged to look into HTTP
>> bindings for publicly distributed SDKs.
>>
>> Using HTTP would allow us to put the server behind an Apache HTTPD server
>> (for example) and to take advantage of lots of existing protocol
>> implementations.
>>
>> Marlon
>>
>>
>