Print

[jz28]

sounds like you are on to something. I discovered a bug, which might be what you are saying about not logging a user out. Basically, the mac addresses of the previously connected xboxes stay there even when they have left a game.

[flat235]

) ... but more importantly, if the client receives the server responses (on the same port if u notice) - then the client is able to receive data from other clients... if they DONT land in 5 seconds, the "Port check failed" kicks in.. We do this because it would be horrible to have loads of people online, who cant actualyl receive game/chat data.. See, the TCP connections will ALWAYS work.. but you MUST verify the 2 UDP ports before allowing the user into the rest of the client.

"When your client calls the script to send an e-mail to another user....."

Bug.. fixing for server model 26..

"There's two HTTP calls (getipadv25.php and epoch25.php) linked two a timer (actually two timers I think), one fires every 20 seconds and the other every 30 seconds. Can these both be combined in to one timer, and would you recommend a 20 second timer or 30 second? These seem to be the only way to maintain a session, and I don't want my client constantly losing a session or flooding the server."

Correct, the calls could (and should) be made at the same time - expect this in model 26... epoch will be folded into getipadv26. 30 seconds will be the chosen interval.

"Are you planning on implementing a logout call in the server? It's not necessary, but it would remove dead entries from the server and make things in sync a little bit more. If there's a heavy load on the server and it takes a minute or so for someone to timeout and be dropped from the currently logged in table, a lot of stale connections could get left in there. It also makes switching users a bit nicer, which I'm going to implement."

It's a possibility.. the server doesnt get affected too much by it not logging out - but I suppose it would be cleaner.. I'll try to get it into model 26.

Thanks

TD