glob2-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[glob2-devel] YOG system update


From: Bradley Arsenault
Subject: [glob2-devel] YOG system update
Date: Tue, 1 May 2007 22:13:02 -0400

I'm just sending out what I have for my YOG system, feel free to
download the patches and take a look at the code. The first patch is
exclusivly the YOG stuff, all 10 of my changsets for it.

The second patch is the game engine stuff that I had done first. I'm
not sure if you need the second to do the first, but I do know that
they don't modify conflicting files (the first patch mostly adds new).
I still don't know how mercurial will deal with this, but I hope that
it will allow one to just import the YOG stuff. If not, import the
other stuff first.

The new YOG system is being done in the following header/source pairs:
   NetConnection, NetListener, NetMessage, YOGGameServer, YOGPlayer,
YOGClient, & NetTestSuite

And I also made a change to YOGConsts, commenting out the current
consts and replacing them with my own.

Note that its not going to compile, no matter how you import the
changes. I haven't even attempted compiling the code yet, so there are
probably allot of small errors I have overlooked. Plus the fact that
it doesn't yet integrate into Glob2 yet, and the changes in YOGConsts
will have a rippling effect.

So far I've got the low level communication classes done, and some of
the YOG communication done. I haven't implemented the RSA encryption
of passwords yet, and I haven't implemented password stoarge on the
server yet either. Yet most of the communication is functional, and
sends only a few bytes of data, making the protocol very compact.

I've chosen to model the client as much as a self contained system as
possible. Right now, it sets a state that it needs login information,
and another object (presumably the caller) has to check this state,
and provide it with login information. This means that the YOGClient
requires other code to function, but that other code can be anything
and is entirely external. Usually, this would be the GUI. After it
sees the request for login information, it would retrieve it from the
user.

Comments & suggestions are welcome.
--
Really. I'm not lieing. Bradley Arsenault.

Attachment: patch1.txt
Description: Text document

Attachment: patch2.txt
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]