Create documentation of the implementation approaches

[dietmarkuehl]

This documentation is intended to be a road map to the beman::net29 implementation to help contributors to find their way around. This documentation would be specific to the choices of this particular implementation rather than something [necessarily] common to implementations of the specification.

Here are some things which need to be covered:

1. Document the idiosyncrasies of how file handles are represented and why that is done.
2. Document the key abstractions/system customizations (native_handle_type, io_base, etc.).
3. Document context_base and its intended use.
4. Document how supported asynchronous operations are handles (see, e.g., operation.hpp and why that is done.
5. The list above is probably incomplete.

[ahendre2010]

Hi @dietmarkuehl ,
I did not yet read the paper but this server library sounds very interesting to me. Saw beman project presentation on cppcon yt channel.

I am new to cpp standards workflows, but have been working on couple of enterprise level C++ projects.

So if you think it's cool, I am willing to spend my spare time working on this project.

[dietmarkuehl]

Hi @dietmarkuehl , I did not yet read the paper but this server library sounds very interesting to me. Saw beman project presentation on cppcon yt channel.

I am new to cpp standards workflows, but have been working on couple of enterprise level C++ projects.

So if you think it's cool, I am willing to spend my spare time working on this project.

Hello @ahendre2010 !

Contributions are certainly welcome! There are plenty things to do with different levels of complexity:

• Try things out and report issues.
• Create examples.
• Add a "readiness" sender (poll?).
• Implement support of Windows (which should be similar to the UNIX support but the types are named different).
• Design/implement a test context.
• etc.

I don't know what your area of interest is. Send corresponding PRs or ask questions (probably in an issue)! I'll also try to update the README with the updated plan: while the existing code is likely becoming the basis of this implementation, the interface is probably moving more towards a TAPS-like interface. Also see the current proposal (P3482) in this space.

[ahendre2010]

Hello @dietmarkuehl ,
I am able to successfully compile 6972ef9 (although with warnings) & run test on Fedora Linux with GCC 14.2.1. But recent changes are causing me to install libasan & libubsan. If these are mandatory dependencies can I add these to readme doc at repo root?

[dietmarkuehl]

Hello Akshay,a pull request improving the documentation/README is certainly appreciated. If you can post the warnings somewhere I’d also look at fixing these (or create a pull request fixing warnings).I’d think that the sanitizers aren’t strictly required: for a release bulild (preset gcc-release) they shouldn’t be dragged in. I haven’t tested that, though.Thanks,   DietmarOn 1 Feb 2025, at 13:01, Akshay ***@***.***> wrote: Hello @dietmarkuehl , I am able to successfully compile 6972ef9 (although with warnings) & run test on Fedora Linux with GCC 14.2.1. But recent changes are causing me to install libasan & libubsan. If these are mandatory dependencies can I add these to readme doc at repo root? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>