[tp-devel] LibTpProtoCSCodeGenerator first steps

[tp-devel] LibTpProtoCSCodeGenerator first steps

Krzysztof Sobolewski jezuch at interia.pl
Mon May 5 17:42:13 EDT 2008


Marcel Hauf pisze:

> Yeah, right but .Net provides a TcpClient class to handle a net
> connection easier.
> But I prefer sockets.

Oh, yeah, I'm not familiar with .NET, obviously...

> The client library receives binary "code" which will be deserialized by
> a BinarySerializer with the help of the protocol library.
> This means the protocol library must be 100% compatible to the server
> protocol library, I´m correct?

It's the nature of protocols that the implementation has to be 100%
compatible, isn't it... Parts of libtpproto-java could be used on the server
side, because the wire format, obviously, is the same and only the concrete
frames differ.
But maybe I don't understand the question :)
-- 
KS
"To an engineer, everyone looks like a chimp" - Dilbert

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://mail.thousandparsec.net/pipermail/tp-devel/attachments/20080505/ccf92193/attachment.pgp 


More information about the tp-devel mailing list