Thousand Parsec: Mail Archives

2008/5/5 Krzysztof Sobolewski <jezuch at interia.pl>:

> 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...

No problem. I haven´t figured out by myself all .Net classes and functions
yet.

>
> > 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 :)

Not if it is simple plain text. There you can only pick up the command and
left out the attributes.
In binary form I think it is not possible to only have a class which gets
deserialized which only stores the command and no attributes.
It would have been better if I had written it without the question mark(?)
(This is not a question).

~ Marcel Hauf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.thousandparsec.net/pipermail/tp-devel/attachments/20080506/66f82774/attachment-0001.htm