Return-Path: 
 <dev-return-12523-apmail-airavata-dev-archive=airavata.apache.org@airavata.apache.org>
X-Original-To: apmail-airavata-dev-archive@www.apache.org
Delivered-To: apmail-airavata-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4B79E11182
	for <apmail-airavata-dev-archive@www.apache.org>;
 Thu,  3 Jul 2014 02:32:13 +0000 (UTC)
Received: (qmail 71856 invoked by uid 500); 3 Jul 2014 02:32:11 -0000
Delivered-To: apmail-airavata-dev-archive@airavata.apache.org
Received: (qmail 71810 invoked by uid 500); 3 Jul 2014 02:32:11 -0000
Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@airavata.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@airavata.apache.org>
List-Post: <mailto:dev@airavata.apache.org>
List-Id: <dev.airavata.apache.org>
Reply-To: dev@airavata.apache.org
Delivered-To: mailing list dev@airavata.apache.org
Received: (qmail 71736 invoked by uid 99); 3 Jul 2014 02:32:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 02:32:11 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of
 danushka.menikkumbura@gmail.com designates 209.85.220.171 as permitted
 sender)
Received: from [209.85.220.171] (HELO mail-vc0-f171.google.com)
 (209.85.220.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 02:32:06 +0000
Received: by mail-vc0-f171.google.com with SMTP id id10so10958331vcb.2
        for <multiple recipients>; Wed, 02 Jul 2014 19:31:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=ng3c5gdsf31EdAAO7ztD0FIubrP9A57r5UQGkG3fAn8=;
        b=DSEud7Lf2ln8QTia60N1ym34Un8hth3AqvAWxM4YFr9OP41wljdcLSIte6sPfGQo50
         duWqFFIMHBYX8ZNok4xN+locGiqlnEzRWGttOkpTafVF6F/w9mdPSy/8HgqgUhHbFYKV
         ZiHi6liNVro+COltt1VmZLcPZcBpeKNJKTjzgCFA80kldw8EJ5RYjzuzUSRMCx7TsLoy
         YHxcLBcrHzLPYVailqq/IOCsGRdUYuJ4CyM3HY/40ECIZEsolUXKuNZ+e9ezERGRnfJs
         kMN2TnSqwPyik0juWDvvfXVMiqtCFstCR9FmwGzoBc85uEUCJE3P669OWKxgo8599YAD
         BY4Q==
X-Received: by 10.52.182.163 with SMTP id ef3mr973762vdc.22.1404354705838;
 Wed, 02 Jul 2014 19:31:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.143.67 with HTTP; Wed, 2 Jul 2014 19:31:25 -0700 (PDT)
In-Reply-To: <53B4539E.8050306@iu.edu>
References: <53B4539E.8050306@iu.edu>
From: Danushka Menikkumbura <danushka.menikkumbura@gmail.com>
Date: Thu, 3 Jul 2014 08:01:25 +0530
Message-ID: 
 <CAF4V=3GWa8t4NknhxuwGiFoFzJbwHEWMW6hLoZ26F3ztk9F4xw@mail.gmail.com>
Subject: Re: Thrift and HTTP
To: dev <dev@airavata.apache.org>
Cc: architecture@airavata.apache.org
Content-Type: multipart/alternative; boundary=bcaec548a7a36159df04fd40cf8b
X-Virus-Checked: Checked by ClamAV on apache.org

--bcaec548a7a36159df04fd40cf8b
Content-Type: text/plain; charset=UTF-8

My understanding is that Thrift over HTTP hinders some of the strengths in
native Thrift. Simplicity, ability to support encryption, compression, NIO
and persistent connections just to name a few. But yes, being able to have
the server behind HTTPD is on the plus side.

Danushka


On Thu, Jul 3, 2014 at 12:16 AM, 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
>
>

--bcaec548a7a36159df04fd40cf8b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>My understanding is that Thrift over HTTP hinders som=
e of the strengths in native Thrift. Simplicity, ability to support encrypt=
ion, compression, NIO and persistent connections just to name a few. But ye=
s, being able to have the server behind HTTPD is on the plus side.<br>

<br></div>Danushka<br></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Thu, Jul 3, 2014 at 12:16 AM, Marlon Pierce <span dir=
=3D"ltr">&lt;<a href=3D"mailto:marpierc@iu.edu" target=3D"_blank">marpierc@=
iu.edu</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I&#39;m curious if anyone has looked into ru=
nning Thrift over HTTP. =C2=A0We are using TThreadPoolServer for the server=
 and TServerSocket for transport in AiravataAPIServer.java, but we&#39;re b=
eing encouraged to look into HTTP bindings for publicly distributed SDKs.<b=
r>


<br>
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 implementat=
ions.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Marlon<br>
<br>
</font></span></blockquote></div><br></div>

--bcaec548a7a36159df04fd40cf8b--