Simple, modern, C++ socket library.
This is a fairly low-level C++ wrapper around the Berkeley sockets library using socket, acceptor, and connector classes that are familiar concepts from other languages.
The base socket class wraps a system socket handle, and maintains its lifetime. When the C++ object goes out of scope, it closes the underlying socket handle. Socket objects are generally moveable but not copyable. A socket can be transferred from one scope (or thread) to another using std::move().
The library currently supports: IPv4 and IPv6 on Linux, Mac, and Windows. Other *nix and POSIX systems should work with little or no modification.
Unix-Domain Sockets are available on *nix systems that have an OS implementation for them.
Support for secure sockets using either the OpenSSL or MbedTLS libraries was recently added with basic coverage. This will continue to be expanded in the near future.
There is also some experimental support for CAN bus programming on Linux using the SocketCAN package. This gives CAN bus adapters a network interface, with limitations dictated by the CAN message protocol.
All code in the library lives within the sockpp C++ namespace.
The 'master' branch is starting the move toward the v2.0 API, and is particularly unstable at the moment. You're advised to download the latest release for general use.
Version 1.0 is releaed!
As breaking changes were starting to accumulate in the current development branch, the decision was made to release the API that has been fairly stable for the last few years as 1.0. This is from the latest v0.8.x line. That will make things going forward less confusing and allow us to maintain the v1.x branch.
Version 2.0 development is underway.
The idea of having "stateless" I/O operations introduced in PR #17, (which was never fully merged) is coming in the 2.0 API with a result<T> class. It will be generic over the "success" return type with errors being represented by a std::error_code. This should help to significantly reduce platform issues for tracking and reporting errors.
Using a uniform result type removes the need for exceptions in most functions, except maybe constructors. In those cases where the function might throw, a comparable noexcept function will also be provided which can set an error code parameter instead of throwing. So the library can be used without any exceptions if so desired by the application.
All functions that might fail due to a system error will return a result. That will eliminate the need for the "last error", and thus the cached last error variable in the socket class will disappear. The socket classes will then only wrap the socket handle, making them safer to share across threads in the same way a handle can be shared - typically with one thread for reading and another for writing.
Some work has also begun to incorporate Secure Sockets into a 2.x release of the library using either OpenSSL or MbedTLS libraries, or (likely), a build-time choice for one or the other. PR #17, which has been sitting dormant for a few years is being merged and updated, along with new work to do something comparable with OpenSSL. You will be able to chose one secure library or the other when building sockpp.
The 2.0 version will also move up to C++17 and CMake v3.12 or later.
To keep up with the latest announcements for this project, follow me at:
Mastodon: @fpagliughi@fosstodon.org
Twitter: @fmpagliughi
If you're using this library, tweet at me or send me a message, and let me know how you're using it. I'm always curious to see where it winds up!
The library, when installed can normally be discovered with find_package(sockpp). It uses the namespace Sockpp and the library name sockpp.
A simple CMakeLists.txt file might look like this:
cmake_minimum_required(VERSION 3.12)
project(mysock VERSION 1.0.0)
find_package(sockpp REQUIRED)
add_executable(mysock mysock.cpp)
target_link_libraries(mysock Sockpp::sockpp)
Contributions are accepted and appreciated. New and unstable work is done in the develop branch Please submit all pull requests against that branch, not master.
For more information, refer to: CONTRIBUTING.md
CMake is the supported build system.
- A conforming C++-14 compiler.
- gcc v5.0 or later (or) clang v3.8 or later.
- Visual Studio 2015, or later on WIndows.
- CMake v3.12 or newer.
- Doxygen (optional) to generate API docs.
- Catch2 (optional) v2.x or v3.x to build and run unit tests.
To build with default options:
$ cd sockpp
$ cmake -Bbuild .
$ cmake --build build/
To install:
$ cmake --build build/ --target install
The library has several build options via CMake to choose between creating a static or shared (dynamic) library - or both. It also allows you to build the example options, and if Doxygen is installed, it can be used to create documentation.
| Variable | Default Value | Description |
|---|---|---|
| SOCKPP_BUILD_SHARED | ON | Whether to build the shared library |
| SOCKPP_BUILD_STATIC | OFF | Whether to build the static library |
| SOCKPP_BUILD_DOCUMENTATION | OFF | Create and install the HTML based API documentation (requires Doxygen) |
| SOCKPP_BUILD_EXAMPLES | OFF | Build example programs |
| SOCKPP_BUILD_TESTS | OFF | Build the unit tests (requires Catch2) |
| SOCKPP_WITH_CAN | OFF | Include SocketCAN support. (Linux only) |
Set these using the '-D' switch in the CMake configuration command. For example, to build documentation and example apps:
$ cd sockpp
$ cmake -Bbuild -DSOCKPP_BUILD_DOCUMENTATION=ON -DSOCKPP_BUILD_EXAMPLES=ON .
$ cmake --build build/
To build the library with secure socket support, a TLS library needs to be chosen to provide support. Currently OpenSSL or MbedTLS can be used.
Chose one of the following when configuring the build:
| Variable | Default Value | Description |
|---|---|---|
| SOCKPP_WITH_MBEDTLS | OFF | Secure Sockets with MbedTLS |
| SOCKPP_WITH_OPENSSL | OFF | Secure Sockets with OpenSSL |
The sockpp library currently supports MbedTLS v3.3. When building that library, the following configuration options should be defined in the config file, include/mbedtls/mbedtls_config.h
#define MBEDTLS_X509_TRUSTED_CERTIFICATE_CALLBACK
To support threading:
#define MBEDTLS_THREADING_PTHREAD
#define MBEDTLS_THREADING_C
and set the CMake build option:
LINK_WITH_PTHREAD:BOOL=ON
Note that the options in the config file should already be present in the file but commented out by default. Simply uncomment them, save, and build.
The sockpp OpenSSL wrapper is currenly being built and tested with OpenSSL v3.0
TCP and other "streaming" network applications are usually set up as either servers or clients. An acceptor is used to create a TCP/streaming server. It binds an address and listens on a known port to accept incoming connections. When a connection is accepted, a new, streaming socket is created. That new socket can be handled directly or moved to a thread (or thread pool) for processing.
Conversely, to create a TCP client, a connector object is created and connected to a server at a known address (typically host and socket). When connected, the socket is a streaming one which can be used to read and write, directly.
For IPv4 the tcp_acceptor and tcp_connector classes are used to create servers and clients, respectively. These use the inet_address class to specify endpoint addresses composed of a 32-bit host address and a 16-bit port number.
The tcp_acceptor is used to set up a server and listen for incoming connections.
int16_t port = 12345;
sockpp::tcp_acceptor acc(port);
if (!acc)
report_error(acc.last_error_str());
// Accept a new client connection
sockpp::tcp_socket sock = acc.accept();
The acceptor normally sits in a loop accepting new connections, and passes them off to another process, thread, or thread pool to interact with the client. In standard C++, this could look like:
while (true) {
// Accept a new client connection
sockpp::tcp_socket sock = acc.accept();
if (!sock) {
cerr << "Error accepting incoming connection: "
<< acc.last_error_str() << endl;
}
else {
// Create a thread and transfer the new stream to it.
thread thr(run_echo, std::move(sock));
thr.detach();
}
}
The hazards of a thread-per-connection design is well documented, but the same technique can be used to pass the socket into a thread pool, if one is available.
See the tcpechosvr.cpp example.
The TCP client is somewhat simpler in that a tcp_connector object is created and connected, then can be used to read and write data directly.
sockpp::tcp_connector conn;
int16_t port = 12345;
if (!conn.connect(sockpp::inet_address("localhost", port)))
report_error(conn.last_error_str());
conn.write_n("Hello", 5);
char buf[16];
ssize_t n = conn.read(buf, sizeof(buf));
See the tcpecho.cpp example.
UDP sockets can be used for connectionless communications:
sockpp::udp_socket sock;
sockpp::inet_address addr("localhost", 12345);
std::string msg("Hello there!");
sock.send_to(msg, addr);
sockpp::inet_address srcAddr;
char buf[16];
ssize_t n = sock.recv(buf, sizeof(buf), &srcAddr);
See the udpecho.cpp and udpechosvr.cpp examples.
The same style of connectors and acceptors can be used for TCP connections over IPv6 using the classes:
inet6_address
tcp6_connector
tcp6_acceptor
tcp6_socket
udp6_socket
Examples are in the examples/tcp directory.
The same is true for local connection on *nix systems that implement Unix Domain Sockets. For that use the classes:
unix_address
unix_connector
unix_acceptor
unix_socket (unix_stream_socket)
unix_dgram_socket
Examples are in the examples/unix directory.
The Controller Area Network (CAN bus) is a relatively simple protocol typically used by microcontrollers to communicate inside an automobile or industrial machine. Linux has the SocketCAN package which allows processes to share acces to a physical CAN bus interface using sockets in user space. See: Linux SocketCAN
At the lowest level, CAN devices write individual packets, called "frames" to a specific numeric addresses on the bus.
For examle a device with a temperature sensor might read the temperature peroidically and write it to the bus as a raw 32-bit integer, like:
can_address addr("CAN0");
can_socket sock(addr);
// The agreed ID to broadcast temperature on the bus
canid_t canID = 0x40;
while (true) {
this_thread::sleep_for(1s);
// Write the time to the CAN bus as a 32-bit int
int32_t t = read_temperature();
can_frame frame { canID, &t, sizeof(t) };
sock.send(frame);
}
A receiver to get a frame might look like this:
can_address addr("CAN0");
can_socket sock(addr);
can_frame frame;
sock.recv(&frame);
The socket class hierarchy is built upon a base socket class. Most simple applications will probably not use socket directly, but rather use derived classes defined for a specific address family like tcp_connector and tcp_acceptor.
The socket objects keep a handle to an underlying OS socket handle and a cached value for the last error that occurred for that socket. The socket handle is typically an integer file descriptor, with values >=0 for open sockets, and -1 for an unopened or invalid socket. The value used for unopened sockets is defined as a constant, INVALID_SOCKET, although it usually doesn't need to be tested directly, as the object itself will evaluate to false if it's uninitialized or in an error state. A typical error check would be like this:
tcp_connector conn({"localhost", 12345});
if (!conn)
cerr << conn.last_error_str() << std::endl;
The default constructors for each of the socket classes do nothing, and simply set the underlying handle to INVALID_SOCKET. They do not create a socket object. The call to actively connect a connector object or open an acceptor object will create an underlying OS socket and then perform the requested operation.
An application can generally perform most low-level operations with the library. Unconnected and unbound sockets can be created with the static create() function in most of the classes, and then manually bind and listen on those sockets.
The socket::handle() method exposes the underlying OS handle which can then be sent to any platform API call that is not exposed by the library.
A socket object is not thread-safe. Applications that want to have multiple threads reading from a socket or writing to a socket should use some form of serialization, such as a std::mutex to protect access.
A socket can be moved from one thread to another safely. This is a common pattern for a server which uses one thread to accept incoming connections and then passes off the new socket to another thread or thread pool for handling. This can be done like:
sockpp::tcp6_socket sock = acc.accept(&peer);
// Create a thread and transfer the new socket to it.
std::thread thr(handle_connection, std::move(sock));
In this case, handle_connection would be a function that takes a socket by value, like:
void handle_connection(sockpp::tcp6_socket sock) { ... }
Since a socket can not be copied, the only choice would be to move the socket to a function like this.
It is a common patern, especially in client applications, to have one thread to read from a socket and another thread to write to the socket. In this case the underlying socket handle can be considered thread safe (one read thread and one write thread). But even in this scenario, a sockpp::socket object is still not thread-safe due especially to the cached error value. The write thread might see an error that happened on the read thread and visa versa.
The solution for this case is to use the socket::clone() method to make a copy of the socket. This will use the system's dup() function or similar create another socket with a duplicated copy of the socket handle. This has the added benefit that each copy of the socket can maintain an independent lifetime. The underlying socket will not be closed until both objects go out of scope.
sockpp::tcp_connector conn({host, port});
auto rdSock = conn.clone();
std::thread rdThr(read_thread_func, std::move(rdSock));
The socket::shutdown() method can be used to communicate the intent to close the socket from one of these objects to the other without needing another thread signaling mechanism.
See the tcpechomt.cpp example.