Well, what I'm really curious about is a fully non-blocking c++ client. What I'm doing now is sending the send_'s, setting cseqids myself, and then sorting out the responses based on the rseqid, that's ok, but the recv call in TSocket is still a blocking call. Since it's been an open issue for so long, I'm curious if there are others working on it, or deep seeded reasons why it's not been done that I just don't know about.
-----Original Message----- From: Mayan Moudgill [mailto:[email protected]] Sent: Tuesday, March 16, 2010 7:41 PM To: [email protected]; Daniel Kluesing Subject: Re: async c++ client / THRIFT-1 I'm guessing you want the abilitiy to separate the calls and receives on a client; is that correct? Thanks Mayan Daniel Kluesing wrote: > I wanted/needed something approximating async requests on the client - > directly call send_ stuff, do unrelated stuff that might fail, directly call > recv_ stuff - so I hacked into the c++ generator on 0.2.0 a bit more support > for cseqid and rseqid. I did this somewhat quickly and while it works for my > purposes, it isn't the 'right' thing to do. Is there any news on > http://issues.apache.org/jira/browse/THRIFT-1 or anyone working on a proper > nonblocking c++ client? (I saw the spotify ASIO patch) > > (and if anyone out there wants similar functionality, I can port my changes > to trunk and make a patch, I didn't bother since this has lain dormant for > quite a while, so I'm guessing interest is low) >
