thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Porterfield <justin.porterfi...@gmail.com>
Subject Re: A simple HTTP transport?
Date Thu, 28 Mar 2013 19:35:50 GMT
Here also is an example from the Ruby test specs:

https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=blob;f=lib/rb/spec/thin_http_server_spec.rb;hb=HEAD

Justin Porterfield


On Thu, Mar 28, 2013 at 2:24 PM, Roger Meier <roger@bufferoverflow.ch>wrote:

> depends on language you are using, for C++ THttpServer, here is the
> example:
> https://git-wip-us.apache.org/**repos/asf?p=thrift.git;a=blob;**
> f=test/cpp/src/TestServer.cpp;**hb=HEAD<https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=blob;f=test/cpp/src/TestServer.cpp;hb=HEAD>
>
> ;-r
>
> Quoting Srikanth Kandula <kandula@gmail.com>:
>
>  Hi,
>>
>> I am wondering whether there is a simple way to use http as the transport
>> without putting up a web server?
>>
>> For example, when clients speak using THttpClient, is there an easy way to
>> parse these messages at the server?
>>
>> It seems that all we need is a processor on the server that eats the http
>> request and headers out of the input stream before handing off the rest to
>> the actual processors. It would also have to tunnel responses back via
>> http.  Am I missing something?
>>
>> Cheers,
>> -Srikanth
>>
>
>
>

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