Works for me. I have started my writeup at https://lolut.utbm.info/svn/taspring_li ... ingClient/NMDANGE wrote:Something simple like...
[2 byte size][2 byte id][body]
in the commands.* files.
(Yes, should be in a database)
Multiplayer
Moderator: Moderators
Ok, looks good so far. Don't worry about sending a null-terminated string. I use NULL already when I send text to delimit fields. It makes it easier to send to a C++ client.
The url for registration is
http://www.phoenixworx.org/aspnet/register.aspx
Though I suppose it is a good idea to allow the server to send it, since it could change...
The url for registration is
http://www.phoenixworx.org/aspnet/register.aspx
Though I suppose it is a good idea to allow the server to send it, since it could change...
-
jouninkomiko
- Posts: 436
- Joined: 26 Aug 2004, 08:11
i used straight text for ease. i had to crank out this client pretty quickly and it seemed like a good alternative -KISS. i know the client can be improved, greatly in fact. However, you guys want a secure protocol though for a gaming lobby? ... why? and NMDANGE, what's wrong with having everything done in text? the information passed is very simple.
Xon - so say you pass a hash instead of plain text. if someone really wanted to steal your name, they'd just capture your hash in the same way they would capture your password and hack the client to send that instead of the password.
on a side note, i have about half the protocol documented, which i'll be posting soon, in case anyone needs it.
i didnt really plan on taking the client much further than it is at the moment - i want to work on an AI. but i'd be more than glad to help with a new client that is platform independant, especially if we can integrate it into PW. i wish i had some one's help making the gui when i started, thing's would've ended up alot better
it's a shame that my work seems to be made obsolete already, i didn't really expect a turnout of people willing to help on the lobby itself...
Xon - so say you pass a hash instead of plain text. if someone really wanted to steal your name, they'd just capture your hash in the same way they would capture your password and hack the client to send that instead of the password.
on a side note, i have about half the protocol documented, which i'll be posting soon, in case anyone needs it.
i didnt really plan on taking the client much further than it is at the moment - i want to work on an AI. but i'd be more than glad to help with a new client that is platform independant, especially if we can integrate it into PW. i wish i had some one's help making the gui when i started, thing's would've ended up alot better
it's a shame that my work seems to be made obsolete already, i didn't really expect a turnout of people willing to help on the lobby itself...Updates
Don't know if you're still checking here, but have you posted specs for this?jouninkomiko wrote: on a side note, i have about half the protocol documented, which i'll be posting soon, in case anyone needs it.
For anyone working in this area, I'm still pushing at it, but I've never done communication between untrustable devices before and it is slow going. I'm making sure everything is done properly rather than fast, so this will be the last time a rewrite is needed.
The server is made to support multiple protocols. The protocol that the current client uses makes a number of assumptions because the client was written to use a different server originally. It would be better to have the protocol and its code in the server tailored for Spring specifically. The server supports features that the current client isn't designed for, and we'd be limiting Spring to what the current client expects.
If you mean the current PW client that is TA only...well...eventually it'll get relpaced with a multi-game client, but I'm a server programmer and it's not really definite who would be doing a new client.
I'd just like to take whatever client you guys are using or plan on using, with whatever protocol you want, and get it to talk to the PW server, which is relatively simple given the way I wrote it, I just need to know what the protocol is really.
I'd just like to take whatever client you guys are using or plan on using, with whatever protocol you want, and get it to talk to the PW server, which is relatively simple given the way I wrote it, I just need to know what the protocol is really.