thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Casagrande, Norman" <nor...@last.fm>
Subject RE: Non-blocking C++ client?
Date Mon, 29 Jun 2009 15:34:04 GMT
> As far as Thrift goes -- it sounds like I now need to look into
> timeouts, and the Deferred modifications needed in the C++ stubs.

Do you need a sync or async timeout? The two behave quite differently in
ASIO.

--
Norman


> -----Original Message-----
> From: Bruce Simpson [mailto:bms@incunabulum.net]
> Sent: 27 June 2009 13:48
> To: thrift-user@incubator.apache.org
> Subject: Re: Non-blocking C++ client?
> 
> Bruce Simpson wrote:
> >
> > Pardon my questions, I am still trying to get a feel for the
> > Boost.ASIO model and how it can be used to implement Thrift within
our
> > existing code base in XORP.   Timeouts on Thrift RPC are a very
> > desirable feature for us.
> 
> OK. I digested third_party_lib.cpp from Boost's ASIO examples briefly
> yesterday -- and it seems to map neatly onto what we currently have in
> XORP for I/O -- the select() reactor -- however ASIO exists as
headers,
> not library.
> 
> Runtime footprint with ASIO is probably a matter of importing the
> necessary template classes into C++ translation units, and devising
> linkage as appropriate.  ASIO is still a lot of refactoring for us,
but
> as I say, it seems to correspond well with what evolved in XORP over
the
> last 7 years when alternatives were either not available or too fat.
> 
> As far as Thrift goes -- it sounds like I now need to look into
> timeouts, and the Deferred modifications needed in the C++ stubs.
> 
> It is likely we'd need to drop Windows support in the re-spin, but
that
> was kind of looming anyway -- as per my second post to this list -- MS
> don't seem to have their act together with the free toolchains. I'll
see
> if I can get any sense out of them with that later on.
> 
> cheers,
> BMS

Mime
View raw message