You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by Mi...@Dell.com on 2010/07/13 17:06:24 UTC

new AsyncClient stuff in java.

I am considering using thrift for a project, and am intrigued by the new AsyncClient stuff in the java stack.  I have a question arising from very early prototyping, and I wondered if anyone might be able to give some guidance.  (FWIW, should we use thrift, Dell will likely commit back any work we do to thrift in order to solve our issues, possibly including helping to implement similar AsyncClient functionality in .Net.)

When testing the asyncClient, it seems as though the arguments to my method are not actually included in what is getting sent across to the server.  The server is receiving the request, but when parsing the arguments, ends up with a null... Is this something that someone has already addressed and I need to take the latest stamp, (code is a snapshot from ealy last week), or is this something that's gone unnoticed?

Thanks!
                Mike


Michael Brindamour
Dell  |  Software Engineer
300 Innovative Way
Nashua, NH  03062  USA

Michael_Brindamour@Dell.com
office:  1.603.589.5845


Re: new AsyncClient stuff in java.

Posted by Bryan Duxbury <br...@rapleaf.com>.
Michael -

Thanks for following up on the mailing list. Over on my blog, I mentioned
that I looked into it and there was indeed a bug, which is now fixed at
https://issues.apache.org/jira/browse/THRIFT-818. I'll commit it sometime
this week if I don't hear from anyone.

-Bryan

On Tue, Jul 13, 2010 at 8:06 AM, <Mi...@dell.com> wrote:

> I am considering using thrift for a project, and am intrigued by the new
> AsyncClient stuff in the java stack.  I have a question arising from very
> early prototyping, and I wondered if anyone might be able to give some
> guidance.  (FWIW, should we use thrift, Dell will likely commit back any
> work we do to thrift in order to solve our issues, possibly including
> helping to implement similar AsyncClient functionality in .Net.)
>
> When testing the asyncClient, it seems as though the arguments to my method
> are not actually included in what is getting sent across to the server.  The
> server is receiving the request, but when parsing the arguments, ends up
> with a null... Is this something that someone has already addressed and I
> need to take the latest stamp, (code is a snapshot from ealy last week), or
> is this something that's gone unnoticed?
>
> Thanks!
>                Mike
>
>
> Michael Brindamour
> Dell  |  Software Engineer
> 300 Innovative Way
> Nashua, NH  03062  USA
>
> Michael_Brindamour@Dell.com
> office:  1.603.589.5845
>
>