SocketNS Namespace Reference
Detailed Description
holds socket enumerations and constants
|
Enumerations |
| enum | TransportType_t { SOCK_STREAM = _SYS_SOCK_STREAM,
SOCK_DGRAM = _SYS_SOCK_DGRAM
} |
| | Specifies transport type. TCP is usually a good idea. More...
|
| enum | ConnectionState {
CONNECTION_CLOSED,
CONNECTION_CONNECTING,
CONNECTION_CONNECTED,
CONNECTION_LISTENING,
CONNECTION_CLOSING,
CONNECTION_ERROR
} |
| | Internal TCP/UDP Connection State.
|
| enum | FlushType_t { FLUSH_NONBLOCKING = 0,
FLUSH_BLOCKING
} |
| | Chooses between blocking and non-blocking Wireless Input, Output. Blocking wireless output from the main process will affect the performance of the Aibo, and should only be used for debugging purposes. More...
|
Variables |
|
const int | _SYS_SOCK_STREAM = 1 |
| | aperios doesn't provide SOCK_STREAM, so we will initialize them to these values
|
|
const int | _SYS_SOCK_DGRAM = 2 |
| | aperios doesn't provide SOCK_DGRAM, so we will initialize them to these values
|
Enumeration Type Documentation
Specifies transport type. TCP is usually a good idea.
- Enumerator:
-
| SOCK_STREAM |
TCP: guaranteed delivery, higher overhead. |
| SOCK_DGRAM |
UDP: no guarantees, low overhead. |
Definition at line 36 of file Socket.h.
Chooses between blocking and non-blocking Wireless Input, Output. Blocking wireless output from the main process will affect the performance of the Aibo, and should only be used for debugging purposes.
- Enumerator:
-
| FLUSH_NONBLOCKING |
Writes and Reads return immediately, and are processed by another process, so Main can continue to run. Non-blocking reads require specifying a callback function to handle data received. |
| FLUSH_BLOCKING |
Blocking writes are a good idea for debugging - a blocking write will be transmitted before execution continues to the next statement. Blocking reads should be avoided, since they'll cause a significant slow down in the main process. |
Definition at line 52 of file Socket.h.
|
