Network Protocol - Revision history

Zehra: to rewrite entirely from scratch

2025-11-10T03:20:54Z

to rewrite entirely from scratch

Zehra: /* Connecting to a server */ updated link to GitHub

2016-07-16T19:48:54Z

Connecting to a server: updated link to GitHub

← Older revision		Revision as of 19:48, 16 July 2016
Line 83:		Line 83:

	== Connecting to a server ==		== Connecting to a server ==
	The [~~http~~://~~bzflag.svn.sourceforge~~.~~net/viewvc~~/~~checkout~~/bzflag/~~trunk~~/~~bzflag~~/misc/bzfquery.php bzfquery.php script] is a nice example of how to connect to a server.		The [https://github.com/BZFlag-Dev/bzflag/blob/2.4/misc/bzfquery.php bzfquery.php script] is a nice example of how to connect to a server.

	At the beginning you need to open a socket. Beginning with protocol 0048 you need to send "BZFLAG\r\n\r\n" in order to get any reply. At that time you unfortunately don't know the protocol, so send it by default or your client will probably freeze.		At the beginning you need to open a socket. Beginning with protocol 0048 you need to send "BZFLAG\r\n\r\n" in order to get any reply. At that time you unfortunately don't know the protocol, so send it by default or your client will probably freeze.
Line 109:		Line 109:
	Player [0] sent huge packet length (len=16986), possible attack		Player [0] sent huge packet length (len=16986), possible attack
	Player [0] removed at 2007-04-11 15:52:55: large packet recvd		Player [0] removed at 2007-04-11 15:52:55: large packet recvd


	== Message types ==		== Message types ==

JeffM2501: Isn't really a design document but a set of incomplete references, goes into other categories

2013-02-10T08:08:01Z

Isn't really a design document but a set of incomplete references, goes into other categories

← Older revision		Revision as of 08:08, 10 February 2013
Line 1:		Line 1:
	{{Inaccurate}}		{{Inaccurate}}
	~~{{DesignDocument}}~~

	= Introduction =		= Introduction =
Line 920:		Line 919:
	server can now send over udp		server can now send over udp

			[[Category:Development]]
	[[Category:Concepts]]		[[Category:Concepts]]

Yosef: minor edits - changed email to motto

2011-11-06T16:12:58Z

minor edits - changed email to motto

Yosef: /* Introduction */

2011-11-06T16:05:35Z

Introduction

← Older revision		Revision as of 16:05, 6 November 2011
Line 4:		Line 4:
	= Introduction =		= Introduction =

	BZFlag uses standard IP (Internet) networking protocols. The code is written to the BSD socket interface, with adjustments for winsock on win32 platforms. Future revisions may centralize the network code into one file behind a single class interface to simplify porting to platforms without the BSD socket API.		BZFlag uses standard IP (Internet) networking protocols. The code is written to the BSD socket interface, with adjustments for winsock on win32 platforms. Future revisions may centralize the network code into one file, behind a single class interface, to simplify porting to platforms without the BSD socket API.
	Most communication is non-blocking. That is, reads and sends return immediately instead of waiting for data to become available or to be sent. That's important since BZFlag is a real time game. It can't afford to get stuck waiting for a packet to come in. (The one exception to this is when BZFlag connects to a server, and this should get fixed someday.)		Most communication is non-blocking. That is, reads and sends return immediately instead of waiting for data to become available or to be sent. That's important since BZFlag is a real-time game. It can't afford to get stuck waiting for a packet to come in. (The one exception to this is when BZFlag connects to a server, and this should get fixed someday.)
	Communication is multiplexed using the select() call, which notifies the caller which sockets have data pending for read and/or are ready for sends. Instead of checking for incoming data by trying to read every socket and testing for success, we simply ask the system which sockets have data and read on those only. This also means that we use just a single thread for network communication.		Communication is multiplexed using the select() call, which notifies the caller which sockets have data pending for read and/or are ready for sends. Instead of checking for incoming data by trying to read every socket and testing for success, we simply ask the system which sockets have data and read on those only. This also means that we use just a single thread for network communication.
	BZFlag uses two distinct transport protocols to communicate with the server. Server communication uses TCP/IP for reliability. Live game data communication uses UDP for speed and efficiency. See the other pages for more details.		BZFlag uses two distinct transport protocols to communicate with the server. Server communication uses TCP/IP for reliability. Live game data communication uses UDP for speed and efficiency. See the other pages for more details.


	= Client/Server Communication =		= Client/Server Communication =

Flash: spell check

2007-04-23T04:42:16Z

spell check

Learner: design doc

2007-04-14T17:21:22Z

design doc

← Older revision		Revision as of 17:21, 14 April 2007
Line 1:		Line 1:
	{{Inaccurate}}		{{Inaccurate}}
			{{DesignDocument}}

	= Introduction =		= Introduction =

Ts: Port more of the old stuff

2007-04-12T13:20:05Z

Port more of the old stuff

Show changes

Ts: Partial port from http://bzflag.svn.sourceforge.net/viewvc/checkout/bzflag/trunk/bzflag/doc/guide/NetworkProtocol.xml

2007-04-12T11:58:11Z

Partial port from http://bzflag.svn.sourceforge.net/viewvccheckout: bzflag/trunk/bzflag/doc/guide/NetworkProtocol.xml