Non-Netty client - Any help please, nearly there!
skhalid
shahbaz.khalid at gmail.com
Mon Dec 29 16:13:41 EST 2008
Sorry Trustin - there was a mistake in the code - it should have been the
Message object being sent back, but I was experimenting to see if I could
serialise the object on my own and send it back as an array back to the
client (strangely enough this works, and after stripping the first 23 bytes
in the array I get on the client side, I can convert/cast the rest of the
bytes into my own object).
For the code that I am submitting, there is only one change - the Message
class is actually the Customer class (I only renamed the class in the
original thread post to , uh, look respectable - why would a telnet server
return customer objects?).
But please find the code attached - ignore the other methods for the time
being and only focus on what's going on in the main method of
TCPEchoClientNonblocking class.
I would really appreciate your help.
P.S. The only reason why I am having to revert to a custom NIO client is
that the Android does not like the TimeBasedUuidGenerator class (because
android JVM does not have the java.lang.management.* package). Otherwise I
would have used the netty client.
http://n2.nabble.com/file/n2090326/work8.zip work8.zip
--
View this message in context: http://n2.nabble.com/Non-Netty-client-tp1771503p2090326.html
Sent from the Netty User Group mailing list archive at Nabble.com.
More information about the netty-users
mailing list