|Support Forum Library Source SourceForge Page G3D Web Page|
Abstraction of network (socket) functionality. More...
|Description of an ethernet or wireless ethernet adapter. More...|
|const Array< EthernetAdapter > &||adapterArray () const|
|Returns the available ethernet adapters for the current machine that are online. |
|const Array< uint32 > &||broadcastAddressArray () const|
|Returns the (unique) IP addresses for UDP broadcasting extracted from adapterArray(). |
|void||describeSystem (TextOutput &t)|
|Prints a human-readable description of this machine to the text output stream. |
|void||describeSystem (std::string &s)|
|void||localHostAddresses (Array< NetAddress > &array) const|
|There is often more than one address for the local host. |
|std::string||localHostName () const|
|Returns the name (or one of the names) of this computer. |
|static void||cleanup ()|
|Shuts down the network device (destroying the global instance). |
|static std::string||formatIP (uint32 ip)|
|Prints an IP address to a string. |
|static std::string||formatMAC (const uint8 mac)|
|Prints a MAC address to a string. |
|static NetworkDevice *||instance ()|
|Returns NULL if there was a problem initializing the network. |
Abstraction of network (socket) functionality.
An abstraction over sockets that provides a message-based network infrastructure optimized for sending many small (~500 bytes) messages. All functions always return immediately.
Create only one NetworkDevice per process (a WinSock restriction).
NetworkDevice is technically not thread safe. However, as long as you use different conduits on different threads (or lock conduits before sending), you will encounter no problems sharing the single NetworkDevice across multiple threads. That is, do not invoke the same Conduit's send or receive method on two threads at once.
This assumes that the underlying WinSock/BSD sockets implementation is thread safe. That is not guaranteed, but in practice seems to always be true (see http://tangentsoft.net/wskfaq/intermediate.html#threadsafety)
IP networks use "network byte order" (big-endian) for communicating integers. "Host byte order" is the endian-ness of the local machine (typically little-endian; see System::endian). The C functions htonl() and ntohl() convert 32-bit values between these formats. G3D only ever exposes host byte order, so programmers rarely need to be aware of the distinction.
Returns the available ethernet adapters for the current machine that are online.
Does not include the loopback adapter for localhost.
Returns the (unique) IP addresses for UDP broadcasting extracted from adapterArray().
All are in host byte order.
Shuts down the network device (destroying the global instance).
Prints a human-readable description of this machine to the text output stream.
Prints an IP address to a string.
|ip||In host byte order.|
Prints a MAC address to a string.
Returns NULL if there was a problem initializing the network.
Returns the name (or one of the names) of this computer.