Crossfire Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Client/server protocol



>C->S: MOVE 123 44 45
>A request by the client to move the player (object 123) south (from
>44 to 45).  Remember, that the maps make 0,0 as the upper left corner,
>not lower left as in standard geometry.

 This should be move object 123 to 44 (x), 45 (y).  All map
locations are in x y coordinate form, and not some form that is
embeded in one number.

 As protocol definition, all X Y coordinate values are in that
order, X first, then Y.

 As for removing X support in the server, this can also be done
at some time via a configure option.  People on a very fast network
with a very fast server machine may not really care about client/server.
The main benefits of client server is a little reduced load for
the server, ability to play over slower links, and be able to
have different client interfaces.

 On the last one, a good idea for the client would be to write
a skeleton client that parses the protocol data (as well as init
the link), store the data in the appropriate structures, but
just pseudo code all the actul window calls.  In this way, anyone
that wants to develope a client with a different toolkit
(Xaw, xview, motif) or system just needs to write the appropriate areas,
and not start from scratch or make serious modifications to
a version with the window calls already in palce.

 --Mark