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_brindam...@dell.com
office:  1.603.589.5845

Reply via email to