File SolidSyslogWinsockTcpStream.h¶
FileList > Interface > SolidSyslogWinsockTcpStream.h
Go to the source code of this file
A non-blocking TCP stream over a Winsock socket, for a StreamSender or as the byte transport under a TlsStream. More...
#include "SolidSyslogStream.h"#include "SolidSyslogTcpConnectTimeoutFunction.h"#include "SolidSyslogTransport.h"
Classes¶
| Type | Name |
|---|---|
| struct | SolidSyslogWinsockTcpStreamConfig Tunes SolidSyslogWinsockTcpStream's bounded connect. |
Public Functions¶
| Type | Name |
|---|---|
| struct SolidSyslogStream * | SolidSyslogWinsockTcpStream_Create (const struct SolidSyslogWinsockTcpStreamConfig * config) Draw a TCP stream from the pool; the config's GetConnectTimeoutMs bounds the connect (see the file overview for the stream's behaviour). |
| void | SolidSyslogWinsockTcpStream_Destroy (struct SolidSyslogStream * base) Release the pool slot and close the socket. |
Detailed Description¶
What the stream does through its vtable is the substance:
- Open makes the socket non-blocking (FIONBIO) before connecting, so connect returns WSAEWOULDBLOCK and the wait is bounded by a select() up to the config's GetConnectTimeoutMs (re-read each attempt, so a runtime-tunable value applies on the next reconnect); a refused or unreachable peer fails fast. This deliberately sidesteps Winsock's blocking connect(), which retries a refused loopback port internally for ~2 s before returning.
- Send is all-or-nothing and never blocks the service thread: a short write or any error is taken as a dead connection, so the stream closes itself and the sender reconnects on its next pass.
- Read returns the bytes read, 0 for would-block (WSAEWOULDBLOCK, connection kept), or tears the connection down on peer close or error.
TCP_NODELAY is on, and kernel keepalive (idle ~45s, then 4 x 10s probes via TCP_KEEPIDLE / TCP_KEEPINTVL / TCP_KEEPCNT) surfaces a wedged peer as a failed Send/Read. This adapter leaves the per-connection pending-write cap (TCP_MAXRT and the initial-RTO knobs) at the OS default, so an unacked write relies on the OS-default retransmit behaviour.
The caller must invoke WSAStartup before use and WSACleanup on shutdown; the library does not manage the Winsock lifecycle.
Public Functions Documentation¶
function SolidSyslogWinsockTcpStream_Create¶
Draw a TCP stream from the pool; the config's GetConnectTimeoutMs bounds the connect (see the file overview for the stream's behaviour).
struct SolidSyslogStream * SolidSyslogWinsockTcpStream_Create (
const struct SolidSyslogWinsockTcpStreamConfig * config
)
An exhausted pool (default size 2, for the plain-TCP + TLS-under-TCP pair) falls back to the shared NullStream.
function SolidSyslogWinsockTcpStream_Destroy¶
Release the pool slot and close the socket.
The documentation for this class was generated from the following file Platform/Windows/Interface/SolidSyslogWinsockTcpStream.h