Repository files navigation

Join us on Slack!http://slack.cpp-netlib.org/

Subscribe to the mailing list:https://groups.google.com/forum/#!forum/cpp-netlib

This is a re-do of the work in cpp-netlib/cpp-netlib but updated to the latestC++ standard. This repository is a from-scratch re-imagining of the solution tomodern C++ network programming.

IMPORTANT: This is not an officially supported Google product.

• Provide modern composable components for network programming. We'll providethe middle-level abstractions (connections, messages, encoders/decoders) whichwill work with lower-level abstractions provided by platform-specificinterfaces (POSIX, etc.).

• Bundle higher level protocol implementations that build on top of thecomposable components. This will include a re-imagining for an HTTP client andserver implementation, supporting HTTP 1.0/1.1/2 and even work that's at thebleeding edge of HTTP/3 (QUIC).

• Use the latest C++ standard. There will be no backwards compatibilityconcerns. This is a departure from the earlier attempt at keeping a stableinterface and implementation.

• Develop and Release at HEAD. There will be no development/release branches.All work will be done at HEAD (themaster branch) and shall be

As of January 2019, this repository is empty, and work will commence as soon aswe establish some of the community guidelines. There are some important changesfrom the cpp-netlib/cpp-netlib repository which are worth highlighting:

• License change. We will not be re-using anything from thecpp-netlib/cpp-netlib repository because of licensing differences. Thenetlib repository will be licensed under the Apache 2.0 License with acontributor license agreement for contributors. We've decided to do this to bemore accessible and in-line with the prevailing practice for new open sourceprojects, with better options for sustainable development and hygiene.
• Repository layout. We will be following a simpler repository/code layout, witha flat structure and using subdirectories for logical grouping. This gives usflexibility in the way we add new implementations and simplify the developmentprocess.
• Modern practices. We will use continuous integration, test-driven-development,with a focus on readable, well-tested code. This includes supporting modernbuild systems and packaging/deployment.
• Community driven process. We will involve the community in decisions and inthe development process in a more engaged manner. We will enforce that changesare reviewed, that designs are documented, and that plans are tracked. Most ofall we want to be accountable in the work we're doing and delivering for thecommunity of users and developers.
• Regular releases. With automation in place, we will follow a regular releasecadence that is automated, with minimal human intervention.

This time around we're going to engage the community more effectively. Insteadof a handful of maintainers making changes and decisions by fiat, we willinstitute a review process which encourages everyone in the community to voicetheir thoughts and concerns. We will start with the current maintainers and growthe pool of committers as we grow the community.

We are committed to being an inclusive and encouraging environment where allcontributors who agree to be part of the process are welcome. We have a code ofconduct which we are committed to enforcing (seeCODE_OF_CONDUCT.md forspecifics).