Thousand Parsec: Mail Archives

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

> Marcel Hauf pisze:
>
> > If I have the protocol library what is left?
> >
> >     * Client to server connection, I think I will do this via sockets
> >     * Configuration, should be easy with xml
> >
> > Have I left something out?
>
> Well, I have "configuration" in the form of static factories of the
> Connection object. I'm not sure it's that much to tweak here. Maybe the
> protocol version, but it's parameterized (via generics and the Visitor
> object) and not a concern for the library itself.


I thought about the client library (Which form of connection for example).
I rethought this and I think it should be handled by the client directly not
by the client library.


> As for the connection, the protocol library is basically a way to
> serialize
> frame objects to a stream, so any form of binary stream should do (even
> though libtpproto-java assumes sockets; this might be an interesting thing
> to take just the in and out streams and not bother with that). And I don't
> see an alternative to sockets for network communication... ;)
>
> Yeah, right but .Net provides a TcpClient class to handle a net connection
easier.
But I prefer sockets.

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?

~ Marcel Hauf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.thousandparsec.net/pipermail/tp-devel/attachments/20080505/40370ba5/attachment.htm