Day 0 : 8 June 2022 : Project Ava - Multi-Platform Networking Using C++

My 100 Daze of Code

It's official! I've accepted Alex Kallaway's (@ka11away) 100-days-of-code challenge. Today is Wednesday, 8-June-2022 and I'll be posting to this blog to describe my coding activities for the next 100 days. Code examples to be posted on my Github fork of 100-days-of-code at My100DazeOfCode.

Project Ava - Multi-Platform Networking Using C++

Scoping the project

Ava will be a network communications library written in C++, with an accompanying driver program to provide a command-line interface (CLI) and a test program to validate library internals. We'll start the project on Linux and port it to Windows, macOS and (to some extent) iOS. As a stretch goal, we'll attempt an Android port if we have time.

The library should have a public interface but not expose details of the implementation. The build schemes should support conventional Makefile, CMake, possibly Conan Build Manager, Visual Studio .props, .sln, vcxproj. Debugging support using Visual Code on Linux and macOS can be helped by providing launch.json files appropriate for each platform, wrapping GDB and LLDB access.

The CLI should have a help screen to show command formats. A log file output to capture errors is needed. Piping this into syslog where that is available could be nice. If the library can be wrapped in a service on Windows and run as a daemon on Linux then the CLI could leverage an IPC mechanism to relay commands and allow multiple client sessions.

Network security using a 3rd-party encryption library could be good to have - maybe OpenSSL.



Comments

Post a Comment

Popular posts from this blog

Day 12 : 19 June 2022 : Adding Windows Service Logic

Image
My 100 Daze of Code https://github.com/davidjwalling/100-days-of-code #12 : Adding Windows Service Logic Today, we'll add some Win32 API logic in Ava to install, uninstall and run as a service on Windows. We'll add logic in Driver::Service that check if the program was started with the "service" argument as the first program argument. If so, the Service Control Manager will be invoked to start the program as a service. We'll also check for "install" and "uninstall" program arguments and handle these with logic that installs and uninstalls the program, respectively. In a later post, we'll do the equivalent on Linux and macOS and show how to enable Ava to run as a daemon configured in sysctl. Nowadays there are shortcut methods to install and run an executable as a service on Windows. But I prefer to illustrate the APIs that make this work. Some Code Refactoring Up to now we've been using a pointer-to-implementation (pimpl) method for exp...
Read more

Day 5 : 12 June 2022 : CMake on Windows

Image
 My 100 Daze of Code https://github.com/davidjwalling/100-days-of-code Day 5 : 12 June 2022 : CMake on Windows So far, we've seen using CMake on Linux and MacOS. Also, we've looked at native compilation on Windows using Visual Studio (VS). Today, we'll look at using CMake on Windows. I decided to devote an entire day (hour) to this because there are several ways to invoke CMake on Windows, using different "Generators". A generator will write the inputs to the native build tools. But Wait, There's More ... Before heading to CMake, I wanted to first point out that VS' native tools can build just fine without using CMake, of course. To build using "msbuild," open an x64 Native Tools Command Prompt for Visual Studio - this is provided when VS is installed. Invoke msbuild and pass the solution name and the desired platform and configuration. msbuild ava.sln /p:Platform=x64 /p:Configuration=Debug Repeat for Debug and Release configurations for Win32 an...
Read more

Day 11: 18 June 2022 : Handling Program Arguments

Image
My 100 Daze of Code https://github.com/davidjwalling/100-days-of-code #11 : Handling Program Arguments Up to now we've been carrying around Ava's program argument count (argc) and value array (argv) into a Configure method. Now it's time to start doing something with those values. We'll define four program settings that can be set by passing program arguments: the logging level, path, prefix and suffix, and show examples of using them. Logging Parameter Storage The singleton theLog is instantiated inside the Ava library (libava). Default values for several logging parameters are set by the Log::Init method, which is called both by the Log class constructor and the destructor, by way of the Reset method, so that runtime values are not left in deallocated storage on operating systems that do not automatically clear memory upon deallocation. Logging Parameter Symbols We use namespaces and enums to define symbolic names for the logging parameters so that we have a single lo...
Read more