commit be62c187b6f6265d432c69272df7897095ff4d11
Author: Ivan Polyakov <v1lor at protonmail dot com>
Date:   Sun Oct 2 19:02:57 2022 +0300

    first public release

diff --git a/.clang-format b/.clang-format
new file mode 100644
index 0000000..c4d2194
--- /dev/null
+++ b/.clang-format
@@ -0,0 +1,11 @@
+ColumnLimit: 80
+
+---
+Language: Cpp
+BasedOnStyle: webkit
+
+UseTab: Never
+IndentWidth: 4
+
+PointerAlignment: Right
+SpaceAfterCStyleCast: true
diff --git a/.clangd b/.clangd
new file mode 100644
index 0000000..3bcc16d
--- /dev/null
+++ b/.clangd
@@ -0,0 +1,19 @@
+CompileFlags:
+    Add: [-Wall, -pedantic, -I../include, -DEXTENSIONS_INJA,
+          -DDIST_PATH="/var/www/html"]
+
+
+---
+# Specific C sources
+If:
+    PathMatch: [.*\.c, .*\.h]
+CompileFlags:
+    Add: [-std=gnu99]
+
+
+---
+# Fragment specific to C++ source files
+If:
+    PathExclude: [.*\.c, .*\.h]
+CompileFlags:
+    Add: [-std=c++17, `pkg-config --cflags catch2`]
diff --git a/.drone.yml b/.drone.yml
new file mode 100644
index 0000000..fc56f77
--- /dev/null
+++ b/.drone.yml
@@ -0,0 +1,83 @@
+kind: pipeline
+type: docker
+name: development
+when:
+  event: [ push ]
+  branch: [ dev ]
+
+trigger:
+  branch:
+    - dev
+
+steps:
+  - name: build
+    image: gcc:11-bullseye
+    commands:
+      - apt update -y
+      - apt install -y libfcgi-dev libfcgi-bin doxygen
+      - make all DEBUG=1
+      - make docs
+
+  #- name: tests
+  #  image: gcc:11-bullseye
+  #  commands:
+  #    - apt update -y
+  #    - apt install -y libfcgi-dev libfcgi-bin catch2
+  #    - make -j1 run_tests
+  #    - ./run_tests
+
+  - name: deploy-docs
+    image: drillster/drone-rsync
+    settings:
+      hosts:
+        from_secret: deploy_docs_hosts
+      user:
+        from_secret: deploy_docs_user
+      key:
+        from_secret: deploy_docs_ssh_key
+      target:
+        from_secret: deploy_docs_dev_target
+      source: docs/dist/html/
+
+---
+
+kind: pipeline
+type: docker
+name: production
+when:
+  event: [ push ]
+  branch: [ master ]
+
+trigger:
+  branch:
+    - master
+
+steps:
+  - name: build
+    image: gcc:11-bullseye
+    commands:
+      - apt update -y
+      - apt install -y libfcgi-dev libfcgi-bin doxygen
+      - make all DEBUG=1
+      - make docs
+
+  #- name: tests
+  #  image: gcc:11-bullseye
+  #  commands:
+  #    - apt update -y
+  #    - apt install -y libfcgi-dev libfcgi-bin catch2
+  #    - make -j1 run_tests
+  #    - ./run_tests
+
+  - name: deploy-docs
+    image: drillster/drone-rsync
+    settings:
+      hosts:
+        from_secret: deploy_docs_hosts
+      user:
+        from_secret: deploy_docs_user
+      key:
+        from_secret: deploy_docs_ssh_key
+      target:
+        from_secret: deploy_docs_target
+      source: docs/dist/html/
diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 0000000..347b1ad
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,6 @@
+[*.{c*,h*}]
+indent_style = space
+indent_size = 4
+end_of_line = lf
+trim_trailing_whitespace = true
+max_line_length = 80
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..c83417f
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,47 @@
+# ---> C++
+# Prerequisites
+*.d
+
+# Compiled Object files
+*.slo
+*.lo
+*.o
+*.obj
+
+# Debug symbols
+*.dSYM
+
+# Precompiled Headers
+*.gch
+*.pch
+
+# Compiled Dynamic libraries
+*.so*
+*.dylib
+*.dll
+
+# Fortran module files
+*.mod
+*.smod
+
+# Compiled Static libraries
+*.lai
+*.la
+*.a
+*.lib
+
+# Executables
+*.exe
+*.out
+*.app
+run_tests
+
+# Editors
+*~
+.idea
+.vs
+.vscode
+
+# Dist
+*.tar*
+rapida-*.*
diff --git a/COPYING b/COPYING
new file mode 100644
index 0000000..f288702
--- /dev/null
+++ b/COPYING
@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.
diff --git a/Makefile b/Makefile
new file mode 100644
index 0000000..f3d4547
--- /dev/null
+++ b/Makefile
@@ -0,0 +1,92 @@
+include config.mk
+
+CXXSRC := $(shell find cxx -type f -name '*.cxx')
+CSRC += $(shell find c -type f -name '*.c')
+CXXOBJ := $(CXXSRC:.cxx=.o)
+COBJ := $(CSRC:.c=.o)
+
+#target C and C++ libraries
+all: librapida.a librapida.so librapidaxx.a librapidaxx.so
+
+#target Distribution
+dist: all
+	mkdir -p rapida-$(VERSION)/lib
+	cp -rf README.md COPYING include rapida-$(VERSION)
+	mv librapida.so librapida.so.$(VERSION)
+	mv librapidaxx.so librapidaxx.so.$(VERSION)
+	cp -f *.a *.so* rapida-$(VERSION)/lib
+	tar cf rapida-$(VERSION).tar rapida-$(VERSION)
+	gzip rapida-$(VERSION).tar
+	rm -rf rapida-$(VERSION)
+
+install: all
+	mv librapida.so librapida.so.$(VERSION)
+	mv librapidaxx.so librapidaxx.so.$(VERSION)
+	install librapida.a $(PREFIX)/lib
+	install librapidaxx.a $(PREFIX)/lib
+	install librapida.so.$(VERSION) $(PREFIX)/lib
+	install librapidaxx.so.$(VERSION) $(PREFIX)/lib
+	ln -s $(PREFIX)/lib/librapida.so.$(VERSION) $(PREFIX)/lib/librapida.so
+	ln -s $(PREFIX)/lib/librapidaxx.so.$(VERSION) $(PREFIX)/lib/librapidaxx.so
+	mkdir -p $(PREFIX)/include/rapida
+	cp -f include/* $(PREFIX)/include/rapida
+
+uninstall:
+	rm -f $(PREFIX)/lib/librapida.a
+	rm -f $(PREFIX)/lib/librapidaxx.a
+	rm -f $(PREFIX)/lib/librapida.so*
+	rm -f $(PREFIX)/lib/librapidaxx.so*
+	rm -rf $(PREFIX)/include/rapida
+
+#target Shared C library
+librapida.so: $(COBJ)
+	$(CC) -shared $^ -o $@ $(LDFLAGS)
+
+#target Shared C++ library
+librapidaxx.so: $(COBJ) $(CXXOBJ)
+	$(CXX) -shared $^ -o $@ $(LDFLAGS)
+
+#target Static C library
+librapida.a: $(COBJ)
+	ar rvs $@ $^
+
+#target Static C++ library
+librapidaxx.a: $(COBJ) $(CXXOBJ)
+	ar rvs $@ $^
+
+c/%.o: c/%.c
+	$(CC) $(CFLAGS) -fPIC $< -c -o $@
+
+cxx/%.o: cxx/%.cxx
+	$(CXX) $(CXXFLAGS) $(CXXSTD) -fPIC $< -c -o $@
+
+#target Tests runner
+run_tests: tests/*.cxx librapidaxx.a
+	$(CXX) $(CXXFLAGS) -std=c++17 `pkg-config --cflags catch2` $^ -o $@ $(LDFLAGS)
+
+#target Clear project from generated files
+clean:
+	rm -f **/*.o *.a *.so* run_tests
+
+#target Clear project from generated and distribution files
+distclean: clean
+	rm -f *.tar*
+
+#target Generate documentation
+docs:
+	cd $@ && VERSION=$(VERSION) doxygen
+
+#target Format code
+format:
+	clang-format -Werror -i $(CSRC) $(CXXSRC)
+	clang-format -Werror -i examples/*.c*
+	clang-format -Werror -i tests/*.c* tests/*.h*
+
+#target Show this help
+help:
+	@echo "$$(tput bold)Usage:$$(tput sgr0)\nmake <target> [flags...] [args...]\n"
+	@echo "$$(tput bold)Targets:$$(tput sgr0)";echo;sed -ne"/^#target /{h;s/.*//;:d" -e"H;n;s/^#target //;td" -e"s/:.*//;G;s/\\n#target /---/;s/\\n/ /g;p;}" ${MAKEFILE_LIST}|awk -F --- -v n=$$(tput cols) -v i=29 -v a="$$(tput setaf 6)" -v z="$$(tput sgr0)" '{printf"%s%*s%s ",a,-i,$$1,z;m=split($$2,w," ");l=n-i;for(j=1;j<=m;j++){l-=length(w[j])+1;if(l<= 0){l=n-i-length(w[j])-1;printf"\n%*s ",-i," ";}printf"%s ",w[j];}printf"\n";}'
+	@echo "\n$$(tput bold)Flags (All values other than '0' are true):$$(tput sgr0)";echo;sed -ne"/^#flag /{h;s/.*//;:d" -e"H;n;s/^#flag //;td" -e"s/:.*//;G;s/\\n#flag /---/;s/\\n/ /g;p;}" ${MAKEFILE_LIST}|awk -F --- -v n=$$(tput cols) -v i=29 -v a="$$(tput setaf 6)" -v z="$$(tput sgr0)" '{printf"%s%*s%s ",a,-i,$$1,z;m=split($$2,w," ");l=n-i;for(j=1;j<=m;j++){l-=length(w[j])+1;if(l<= 0){l=n-i-length(w[j])-1;printf"\n%*s ",-i," ";}printf"%s ",w[j];}printf"\n";}'
+	@echo "\n$$(tput bold)Arguments:$$(tput sgr0)";echo;sed -ne"/^#arg /{h;s/.*//;:d" -e"H;n;s/^#arg //;td" -e"s/:.*//;G;s/\\n#arg /---/;s/\\n/ /g;p;}" ${MAKEFILE_LIST}|awk -F --- -v n=$$(tput cols) -v i=29 -v a="$$(tput setaf 6)" -v z="$$(tput sgr0)" '{printf"%s%*s%s ",a,-i,$$1,z;m=split($$2,w," ");l=n-i;for(j=1;j<=m;j++){l-=length(w[j])+1;if(l<= 0){l=n-i-length(w[j])-1;printf"\n%*s ",-i," ";}printf"%s ",w[j];}printf"\n";}'
+
+.PHONY: help clean distclean docs format
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..0cca31f
--- /dev/null
+++ b/README.md
@@ -0,0 +1,35 @@
+Rapida
+======
+[![Build Status](http://drone.vilor.one/api/badges/Rapida/rapida/status.svg)](http://drone.vilor.one/Rapida/rapida)
+[![License: GPL v3](https://img.shields.io/badge/License-GPLv3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0)
+
+Rapida is the C and C++ web framework based on FastCGI protocol.
+
+Dependencies
+------------
+* libfcgi
+* doxygen (to make docs)
+* catch2 (to run tests)
+
+Extensions
+----------
+* [inja](https://github.com/pantor/inja) (template rendering,
+  requires [nlohmann/json](https://github.com/nlohmann/json))
+
+Building
+--------
+You need:
+* GNU Make
+* C compiler with C99 support
+* C++ compiler with C++98 and C++17 support
+
+Run `make help` to see targets, flags and arguments.
+
+Examples
+--------
+See [examples](examples).
+
+License
+-------
+GPLv3 or later. See full text in the [COPYING](COPYING) file
+or in GNU website: https://www.gnu.org/licenses/gpl-3.0-standalone.html
diff --git a/c/app.c b/c/app.c
new file mode 100644
index 0000000..27922a6
--- /dev/null
+++ b/c/app.c
@@ -0,0 +1,174 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "app.h"
+#include <stdlib.h>
+#include <string.h>
+
+#ifdef MT_ENABLED
+#include <pthread.h>
+#endif /* MT_ENABLED */
+
+/*!
+ * \brief Listens new requests by FastCGI protocol.
+ * \param app Pointer to current App instance.
+ * \return Always returns NULL.
+ */
+static void *listen_requests(void *app);
+
+/*!
+ * Handle accepted request.
+ * \param app Application instance.
+ * \param req FastCGI request.
+ */
+static void handle_request(rpd_app *app, FCGX_Request *fcgx_req);
+
+/*!
+ * \brief Selects a route handler based on requested path.
+ * \param app Application instance.
+ * \param req Request.
+ * \return Pointer to route handler.
+ */
+static rpd_route *routes_fabric(rpd_app *app, rpd_req *req);
+
+int rpd_app_create(rpd_app *app, const char *sock_path)
+{
+    app->running = app->sock_id = app->routes_len = 0;
+    app->routes = NULL;
+
+    app->sock_path = strdup(sock_path);
+    if (!app->sock_path)
+        return 1;
+
+    FCGX_Init();
+
+    return 0;
+}
+
+int rpd_app_start(rpd_app *app)
+{
+    if ((app->sock_id = FCGX_OpenSocket(app->sock_path, 10)) < 0) {
+        return 1;
+    }
+
+#ifdef MT_ENABLED
+    pthread_t threads[NTHREADS];
+    for (int i = 0; i < NTHREADS; i++) {
+        pthread_create(&threads[i], 0, listen_requests, (void *) app);
+        pthread_join(threads[i], 0);
+    }
+#else
+    listen_requests((void *) app);
+#endif
+
+    return 0;
+}
+
+int rpd_app_add_route(rpd_app *app, const char *path, rpd_route_cb cb,
+    void *userdata)
+{
+    rpd_route route;
+    if (rpd_route_init(&route, path, cb, userdata))
+        return 1;
+
+    app->routes = (rpd_route *) realloc(app->routes, sizeof(rpd_route) * (app->routes_len + 1));
+    if (!app->routes)
+        return 2;
+
+    app->routes[app->routes_len++] = route;
+    return 0;
+}
+
+static void *listen_requests(void *userdata)
+{
+    rpd_app *app = (rpd_app *) userdata;
+
+    FCGX_Request req;
+    if (FCGX_InitRequest(&req, app->sock_id, 0)) {
+        return 0;
+    }
+
+    app->running = 1;
+    while (app->running) {
+#ifdef MT_ENABLED
+        static pthread_mutex_t accept_mutex = PTHREAD_MUTEX_INITIALIZER;
+        pthread_mutex_lock(&accept_mutex);
+#endif
+
+        int rc = FCGX_Accept_r(&req);
+
+#ifdef MT_ENABLED
+        pthread_mutex_unlock(&accept_mutex);
+#endif
+
+        if (rc < 0) {
+            break;
+        }
+
+#ifdef MT_ENABLED
+        static pthread_mutex_t handle_mutex = PTHREAD_MUTEX_INITIALIZER;
+        pthread_mutex_lock(&handle_mutex);
+#endif
+
+        handle_request(app, &req);
+
+#ifdef MT_ENABLED
+        pthread_mutex_unlock(&handle_mutex);
+#endif
+
+        FCGX_Finish_r(&req);
+    }
+
+    return 0;
+}
+
+static void handle_request(rpd_app *app, FCGX_Request *fcgx_req)
+{
+    rpd_req req;
+    rpd_res res;
+
+    rpd_req_parse(&req, fcgx_req);
+    rpd_res_init(&res, fcgx_req);
+
+    // get route and process request
+    rpd_route *route = routes_fabric(app, &req);
+    if (!route) {
+        return;
+    }
+
+    route->cb(&req, &res, route->userdata);
+
+    rpd_res_send(&res);
+
+    rpd_req_cleanup(&req);
+    rpd_res_cleanup(&res);
+}
+
+static rpd_route *routes_fabric(rpd_app *app, rpd_req *req)
+{
+    const rpd_url *req_path, *route_path = 0;
+    req_path = &req->path;
+
+    for (int i = 0; i < app->routes_len; i++) {
+        route_path = &app->routes[i].path;
+        if (req_path->parts_len != route_path->parts_len)
+            continue;
+
+        int match = 1;
+        for (int j = 0; j < route_path->parts_len && match; j++) {
+            int cur_part_is_dyn = route_path->parts[i][0] == ':';
+            if (!cur_part_is_dyn && strcmp(req_path->parts[i], route_path->parts[i])) {
+                match = 0;
+            }
+        }
+
+        if (!match)
+            continue;
+
+        rpd_keyval_init(&req->params, 0);
+        rpd_url_params_parse_keys(&req->params, route_path);
+        rpd_url_params_parse_vals(&req->params, req_path, route_path);
+        return &app->routes[i];
+    }
+    return NULL;
+}
diff --git a/c/keyval.c b/c/keyval.c
new file mode 100644
index 0000000..23d99cb
--- /dev/null
+++ b/c/keyval.c
@@ -0,0 +1,102 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "keyval.h"
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+
+/*!
+ * \brief Reallocate key-value storage with new capacity.
+ *
+ * \param keyval Key-value storage.
+ * \param capacity New capacity.
+ *
+ * \return Status code.
+ */
+static int rpd_keyval_realloc(rpd_keyval *keyval, int capacity);
+
+int rpd_keyval_init(rpd_keyval *keyval, int capacity)
+{
+    keyval->size = keyval->capacity = 0;
+
+    if (capacity == 0) {
+        keyval->items = NULL;
+        return 0;
+    }
+
+    keyval->items = (rpd_keyval_item *) malloc(sizeof(rpd_keyval_item) * capacity);
+    if (!keyval->items) {
+        return 1;
+    }
+
+    keyval->capacity = capacity;
+    return 0;
+}
+
+int rpd_keyval_insert(rpd_keyval *keyval, const char *key, const char *value)
+{
+    if (!key || !value)
+        return 1;
+    if (keyval->size == keyval->capacity) {
+        int tmp = keyval->capacity == 0 ? 10 : keyval->capacity * 2;
+        if ((tmp = rpd_keyval_realloc(keyval, tmp)))
+            return tmp;
+    }
+
+    rpd_keyval_item *item = rpd_keyval_find(keyval, key);
+    if (item) {
+        free(item->key);
+        item->key = NULL;
+        if (item->val) {
+            free(item->val);
+            item->val = NULL;
+        }
+    } else {
+        item = &keyval->items[keyval->size];
+        keyval->size++;
+    }
+
+    item->key = strdup(key);
+    item->val = strdup(value);
+
+    return item->key && item->val ? 0 : 2;
+}
+
+rpd_keyval_item *rpd_keyval_find(const rpd_keyval *keyval, const char *key)
+{
+    int i = 0;
+    while (i < keyval->size) {
+        if (!strcmp(keyval->items[i].key, key)) {
+            return keyval->items + i;
+        }
+        i++;
+    }
+    return NULL;
+}
+
+void rpd_keyval_cleanup(rpd_keyval *keyval)
+{
+    if (keyval->items) {
+        int i = 0;
+        while (i < keyval->size) {
+            rpd_keyval_item *item = keyval->items + i;
+            free(item->key);
+            if (item->val) {
+                free(item->val);
+            }
+            i++;
+        }
+    }
+    keyval->size = 0;
+}
+
+static int rpd_keyval_realloc(rpd_keyval *keyval, int capacity)
+{
+    keyval->items = realloc(keyval->items, sizeof(rpd_keyval_item) * capacity);
+    if (!keyval->items) {
+        return 1;
+    }
+    keyval->capacity = capacity;
+    return 0;
+}
diff --git a/c/query.c b/c/query.c
new file mode 100644
index 0000000..a3d83aa
--- /dev/null
+++ b/c/query.c
@@ -0,0 +1,94 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "query.h"
+#include "utils.h"
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+
+int rpd_query_parse(rpd_keyval *dest, const char *src)
+{
+    int len = count_char_entries(src, '=');
+    if (!len) {
+        if (dest->items) {
+            free(dest->items);
+        }
+        dest->items = NULL;
+        dest->capacity = 0;
+        dest->size = 0;
+        return 0;
+    }
+
+    char *query = strdup(src);
+    if (!query)
+        return 1;
+
+    dest->items = realloc(dest->items, sizeof(rpd_keyval_item *) * len);
+    if (!dest->items)
+        return 2;
+    dest->capacity = len;
+
+    char *tokens = query, *p = query;
+    int i = 0;
+    while ((p = strsep(&tokens, "&\n")) && i < len) {
+        char *param, *val;
+
+        if (*p == '=')
+            continue;
+        param = strtok(p, "=");
+        val = strtok(NULL, "=");
+
+        if (param) {
+            dest->items[i].key = strdup(param);
+            dest->items[i].val = val ? strdup(val) : NULL;
+            i++;
+        }
+    }
+
+    dest->size = i;
+    dest->capacity = i;
+    free(query);
+    return 0;
+}
+
+char *rpd_query_str(const rpd_keyval *query)
+{
+    size_t len = 0;
+    rpd_keyval_item *item;
+    for (int i = 0; i < query->size; i++) {
+        item = &query->items[i];
+        if (!item->key || !item->val)
+            continue;
+        len += strlen(item->key) + strlen(item->val);
+    }
+
+    /* len + number of key-val delimeters + terminating char */
+    size_t size = len + (query->size - 1) + 1;
+    if (size <= 0)
+        return NULL;
+
+    char *buff = (char *) malloc(sizeof(char) * size);
+    if (!buff)
+        return NULL;
+    buff[size - 1] = '\0';
+
+    size_t offset = 0;
+    for (int i = 0; i < query->size; i++) {
+        item = &query->items[i];
+        if (!item->key || !item->val)
+            continue;
+        offset += sprintf(buff + offset, "%s=%s", item->key, item->val);
+
+        if (i + 1 < query->size) {
+            buff[offset] = '&';
+            offset++;
+        }
+    }
+
+    if (buff[offset - 1] == '&') {
+        buff[offset - 1] = '\0';
+    }
+
+    return buff;
+}
diff --git a/c/request.c b/c/request.c
new file mode 100644
index 0000000..3d242ed
--- /dev/null
+++ b/c/request.c
@@ -0,0 +1,91 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "request.h"
+#include <stdlib.h>
+#include <string.h>
+
+static int rpd_req_read_body(char **dest, FCGX_Request *req);
+
+enum rpd_req_methods rpd_req_smethod(const char *method)
+{
+    if (!strcmp(method, "GET"))
+        return GET;
+    else if (!strcmp(method, "HEAD"))
+        return HEAD;
+    else if (!strcmp(method, "POST"))
+        return POST;
+    else if (!strcmp(method, "PUT"))
+        return PUT;
+    else if (!strcmp(method, "PATCH"))
+        return PATCH;
+    else if (!strcmp(method, "DELETE"))
+        return DELETE;
+    else if (!strcmp(method, "CONNECT"))
+        return CONNECT;
+    else if (!strcmp(method, "OPTIONS"))
+        return OPTIONS;
+    else if (!strcmp(method, "TRACE"))
+        return TRACE;
+    return UNKNOWN;
+}
+
+int rpd_req_parse(rpd_req *dest, FCGX_Request *req)
+{
+    rpd_query_parse(&dest->query, FCGX_GetParam("QUERY_STRING", req->envp));
+
+    dest->method = rpd_req_smethod(FCGX_GetParam("REQUEST_METHOD", req->envp));
+    rpd_url_parse(&dest->path, FCGX_GetParam("DOCUMENT_URI", req->envp));
+    dest->auth = FCGX_GetParam("HTTP_AUTHORIZATION", req->envp);
+    dest->cookie = FCGX_GetParam("HTTP_COOKIE", req->envp);
+    rpd_keyval_init(&dest->params, 0);
+
+    if (dest->method != GET) {
+        if (rpd_req_read_body(&dest->body, req)) {
+            return 2;
+        }
+    } else {
+        dest->body = NULL;
+    }
+
+    return 0;
+}
+
+static int rpd_req_read_body(char **dest, FCGX_Request *req)
+{
+    char *clen = FCGX_GetParam("CONTENT_LENGTH", req->envp);
+    if (!clen)
+        return 1;
+    size_t len = atoll(clen);
+
+    *dest = (char *) malloc(sizeof(char) * (len + 1));
+    if (!*dest)
+        return 2;
+
+    *dest[len] = '\0';
+    FCGX_GetStr(*dest, len, req->in);
+
+    return 0;
+}
+
+void rpd_req_cleanup(rpd_req *req)
+{
+    rpd_keyval_cleanup(&req->params);
+
+    if (req->body) {
+        free(req->body);
+        req->body = NULL;
+    }
+
+    if (req->query.size) {
+        rpd_keyval_cleanup(&req->query);
+    }
+
+    if (req->params.size) {
+        for (int i = 0; i < req->params.size; i++) {
+            rpd_keyval_item *item = req->params.items + i;
+            free(item->val);
+            item->val = NULL;
+        }
+    }
+}
diff --git a/c/response.c b/c/response.c
new file mode 100644
index 0000000..eaf1897
--- /dev/null
+++ b/c/response.c
@@ -0,0 +1,106 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "response.h"
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+
+static size_t calc_res_buff_sz(const rpd_res *res);
+
+void rpd_res_init(rpd_res *dest, FCGX_Request *req)
+{
+    dest->out = req->out;
+
+    dest->status = rpd_res_st_ok;
+    dest->location = dest->content_type = NULL;
+    dest->body = NULL;
+
+    rpd_keyval_init(&dest->cookie, 0);
+}
+
+int rpd_res_send(rpd_res *res)
+{
+    size_t size = calc_res_buff_sz(res);
+
+    char *buff = (char *) malloc(sizeof(char) * size);
+    if (!buff) {
+        return 1;
+    }
+
+    /* header */
+    char *ptr = buff;
+    ptr += sprintf(ptr, "Status: %d\r\n", res->status);
+
+    if (res->content_type) {
+        ptr += sprintf(ptr, "Content-Type: %s\r\n", res->content_type);
+    }
+
+    if (res->location) {
+        ptr += sprintf(ptr, "Location: %s\r\n", res->location);
+    }
+
+    memcpy(ptr, "\r\n", 2);
+    ptr += 2;
+
+    /* body */
+    if (res->body) {
+        int bodylen = strlen(res->body);
+        memcpy(ptr, res->body, bodylen);
+        ptr += bodylen;
+    }
+
+    FCGX_PutS(buff, res->out);
+    free(buff);
+    return 0;
+}
+
+static size_t calc_res_buff_sz(const rpd_res *res)
+{
+    size_t size = res->body ? strlen(res->body) + 2 : 0;
+
+    size += strlen("Status: \r\n") + 3;
+    if (res->location) {
+        size += strlen("Location: \r\n") + strlen(res->location);
+    }
+
+    if (res->content_type) {
+        size += strlen("Content-Type: \r\n") + strlen(res->content_type);
+    }
+
+    if (res->cookie.size) {
+        size += strlen("Set-Cookie: \r\n") * res->cookie.size;
+        for (int i = 0; i < res->cookie.size; i++) {
+            rpd_keyval_item *item = res->cookie.items + i;
+            size += strlen(item->key) + strlen(item->val);
+        }
+    }
+
+    size += 2;
+
+    return size;
+}
+
+void rpd_res_cleanup(rpd_res *res)
+{
+    res->status = rpd_res_st_ok;
+
+    if (res->location) {
+        free(res->location);
+        res->location = NULL;
+    }
+
+    if (res->content_type) {
+        free(res->content_type);
+        res->content_type = NULL;
+    }
+
+    if (res->body) {
+        free(res->body);
+        res->body = NULL;
+    }
+
+    if (res->cookie.capacity) {
+        rpd_keyval_cleanup(&res->cookie);
+    }
+}
diff --git a/c/route.c b/c/route.c
new file mode 100644
index 0000000..d3dc743
--- /dev/null
+++ b/c/route.c
@@ -0,0 +1,19 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "route.h"
+
+int rpd_route_init(rpd_route *dest, const char *path, rpd_route_cb cb,
+    void *userdata)
+{
+    rpd_url url;
+    if (rpd_url_parse(&url, path)) {
+        return 1;
+    }
+
+    dest->path = url;
+    dest->cb = cb;
+    dest->userdata = userdata;
+
+    return 0;
+}
diff --git a/c/url.c b/c/url.c
new file mode 100644
index 0000000..e7b5046
--- /dev/null
+++ b/c/url.c
@@ -0,0 +1,87 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "../include/url.h"
+#include "utils.h"
+#include <stdlib.h>
+#include <string.h>
+
+int rpd_url_parse(rpd_url *dest, const char *src)
+{
+    const char *del = "/";
+    int i = count_char_entries(src, del[0]);
+    if (!i) {
+        dest->parts_len = 0;
+        return 0;
+    }
+
+    dest->parts = (char **) malloc(sizeof(char **) * i);
+    if (!dest->parts) {
+        dest->parts_len = 0;
+        return 2;
+    }
+
+    i = 0;
+    char *tmp, *token;
+    tmp = strdup(src);
+    while ((token = strsep(&tmp, "/"))) {
+        if (!strlen(token))
+            continue;
+        dest->parts[i] = strdup(token);
+        i++;
+    }
+    free(tmp);
+    dest->parts_len = i;
+
+    return 0;
+}
+
+void rpd_url_cleanup(rpd_url *url)
+{
+    int i = 0;
+    while (i < url->parts_len) {
+        free(url->parts[i]);
+        i++;
+    }
+    free(url->parts);
+    url->parts = NULL;
+    url->parts_len = 0;
+}
+
+int rpd_url_params_parse_keys(rpd_keyval *dest, const rpd_url *tpl)
+{
+    int len = 0;
+    for (int i = 0; i < tpl->parts_len; i++) {
+        if (*tpl->parts[i] == ':') {
+            len++;
+        }
+    }
+
+    dest->items = malloc(sizeof(rpd_keyval_item) * len);
+    if (!dest->items)
+        return 1;
+    dest->size = 0;
+    dest->capacity = len;
+
+    for (int i = 0; i < tpl->parts_len; i++) {
+        if (*tpl->parts[i] == ':') {
+            dest->items[dest->size].key = strdup(tpl->parts[i] + 1);
+            dest->size++;
+        }
+    }
+
+    return 0;
+}
+
+int rpd_url_params_parse_vals(rpd_keyval *dest, const rpd_url *url, const rpd_url *tpl)
+{
+    int i = 0, j = 0;
+    while (i < tpl->parts_len) {
+        if (*tpl->parts[i] == ':') {
+            dest->items[j++].val = strdup(url->parts[i]);
+        }
+        i++;
+    }
+
+    return 0;
+}
diff --git a/c/utils.c b/c/utils.c
new file mode 100644
index 0000000..fb2762b
--- /dev/null
+++ b/c/utils.c
@@ -0,0 +1,16 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "utils.h"
+
+int count_char_entries(const char *str, char ch)
+{
+    int cnt = 0;
+    while (*str) {
+        if (*str == ch) {
+            cnt++;
+        }
+        str++;
+    }
+    return cnt;
+}
diff --git a/c/utils.h b/c/utils.h
new file mode 100644
index 0000000..2ca2d9c
--- /dev/null
+++ b/c/utils.h
@@ -0,0 +1,9 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_UTILS_H_ENTRY
+#define RAPIDA_UTILS_H_ENTRY
+
+int count_char_entries(const char *str, char ch);
+
+#endif /* RAPIDA_UTILS_H_ENTRY */
diff --git a/config.mk b/config.mk
new file mode 100644
index 0000000..7b742a2
--- /dev/null
+++ b/config.mk
@@ -0,0 +1,48 @@
+VERSION=0.2.0
+#arg Installation prefix
+PREFIX=/usr/local
+
+CC=gcc
+CFLAGS=-std=gnu99 -pedantic -Iinclude
+CXX=c++
+CXXFLAGS=-pedantic -Iinclude
+CXXSTD=-ansi
+LDFLAGS=-lfcgi
+
+#flag Debug mode
+DEBUG ?= 0
+ifneq ($(DEBUG), 0)
+	CFLAGS+=-Wall -g -DDEBUG_MODE
+	CXXFLAGS+=-Wall -g -DDEBUG_MODE
+else
+	CFLAGS+=-O3
+	CXXFLAGS+=-O3
+endif
+
+
+#arg Additional CXX flags
+ADD_CXXFLAGS =
+ifdef ADD_CXXFLAGS
+	CXXFLAGS+=$(ADD_CXXFLAGS)
+endif
+
+
+#flag Enable inja extension
+EXTENSIONS_INJA ?= 0
+#arg Dist path. Needed only if inja is enabled.
+DIST_PATH = /var/www/html
+ifneq ($(EXTENSIONS_INJA), 0)
+	CXXFLAGS+=-DEXTENSIONS_INJA -DDIST_PATH=\"$(DIST_PATH)\"
+	CXXSTD=-std=c++17
+endif
+
+
+#flag Multithread support
+MT_ENABLED ?= 0
+#arg Number of threads. 8 by default.
+NTHREADS = 8
+ifneq ($(MT_ENABLED), 0)
+	CXXFLAGS+=-DMT_ENABLED -DNTHREADS=$(NTHREADS)
+	CFLAGS+=-DMT_ENABLED -DNTHREADS=$(NTHREADS)
+	LDFLAGS+=-lpthread
+endif
diff --git a/cxx/KeyVal.cxx b/cxx/KeyVal.cxx
new file mode 100644
index 0000000..85ac82c
--- /dev/null
+++ b/cxx/KeyVal.cxx
@@ -0,0 +1,19 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "KeyVal.hxx"
+#include <stdlib.h>
+
+using namespace rpd;
+
+KeyVal::KeyVal()
+    : _keyval((rpd_keyval *) malloc(sizeof(rpd_keyval)))
+{
+    rpd_keyval_init(_keyval, 0);
+}
+
+KeyVal::KeyVal(int capacity)
+    : _keyval((rpd_keyval *) malloc(sizeof(rpd_keyval)))
+{
+    rpd_keyval_init(_keyval, capacity);
+}
diff --git a/cxx/Response.cxx b/cxx/Response.cxx
new file mode 100644
index 0000000..d214a92
--- /dev/null
+++ b/cxx/Response.cxx
@@ -0,0 +1,36 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "Response.hxx"
+
+#ifdef EXTENSIONS_INJA
+#include <inja/inja.hpp>
+#endif
+
+using namespace rpd;
+
+#ifdef EXTENSIONS_INJA
+void Response::render(const char *path, nlohmann::json data)
+{
+    inja::Environment env;
+    inja::Template tpl;
+
+    try {
+        std::string tplpath = DIST_PATH;
+        tplpath += path;
+        tpl = env.parse_template(tplpath);
+    } catch (inja::FileError &e) {
+        std::cerr << e.what() << std::endl;
+        return;
+    }
+
+    try {
+        std::string result = env.render(tpl, data);
+        body(result.c_str());
+    } catch (inja::RenderError &e) {
+        std::cerr << e.what() << std::endl;
+        status(internal_server_error);
+        return;
+    }
+}
+#endif
diff --git a/cxx/Route.cxx b/cxx/Route.cxx
new file mode 100644
index 0000000..e87f20f
--- /dev/null
+++ b/cxx/Route.cxx
@@ -0,0 +1,46 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "Route.hxx"
+#include <stdio.h>
+
+using namespace rpd;
+
+void Route::handle_request(rpd_req *req, rpd_res *res, void *userdata)
+{
+    Route *route = static_cast<Route *>(userdata);
+    const Request reqxx = req;
+    Response resxx = res;
+
+    switch (req->method) {
+    case GET:
+        route->handle_get(reqxx, resxx);
+        break;
+    case HEAD:
+        route->handle_head(reqxx, resxx);
+        break;
+    case POST:
+        route->handle_post(req, resxx);
+        break;
+    case PUT:
+        route->handle_put(req, resxx);
+        break;
+    case PATCH:
+        route->handle_patch(req, resxx);
+        break;
+    case DELETE:
+        route->handle_delete(req, resxx);
+        break;
+    case CONNECT:
+        route->handle_connect(req, resxx);
+        break;
+    case OPTIONS:
+        route->handle_options(req, resxx);
+        break;
+    case TRACE:
+        route->handle_trace(req, resxx);
+        break;
+    case UNKNOWN:
+        break;
+    }
+}
diff --git a/docs/.gitignore b/docs/.gitignore
new file mode 100644
index 0000000..1521c8b
--- /dev/null
+++ b/docs/.gitignore
@@ -0,0 +1 @@
+dist
diff --git a/docs/Doxyfile b/docs/Doxyfile
new file mode 100644
index 0000000..57f400e
--- /dev/null
+++ b/docs/Doxyfile
@@ -0,0 +1,2693 @@
+# Doxyfile 1.9.3
+
+# This file describes the settings to be used by the documentation system
+# doxygen (www.doxygen.org) for a project.
+#
+# All text after a double hash (##) is considered a comment and is placed in
+# front of the TAG it is preceding.
+#
+# All text after a single hash (#) is considered a comment and will be ignored.
+# The format is:
+# TAG = value [value, ...]
+# For lists, items can also be appended using:
+# TAG += value [value, ...]
+# Values that contain spaces should be placed between quotes (\" \").
+
+#---------------------------------------------------------------------------
+# Project related configuration options
+#---------------------------------------------------------------------------
+
+# This tag specifies the encoding used for all characters in the configuration
+# file that follow. The default is UTF-8 which is also the encoding used for all
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the
+# iconv built into libc) for the transcoding. See
+# https://www.gnu.org/software/libiconv/ for the list of possible encodings.
+# The default value is: UTF-8.
+
+DOXYFILE_ENCODING      = UTF-8
+
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
+# double-quotes, unless you are using Doxywizard) that should identify the
+# project for which the documentation is generated. This name is used in the
+# title of most generated pages and in a few other places.
+# The default value is: My Project.
+
+PROJECT_NAME           = "Rapida"
+
+# The PROJECT_NUMBER tag can be used to enter a project or revision number. This
+# could be handy for archiving the generated documentation or if some version
+# control system is used.
+
+PROJECT_NUMBER         = $(VERSION)
+
+# Using the PROJECT_BRIEF tag one can provide an optional one line description
+# for a project that appears at the top of each page and should give viewer a
+# quick idea about the purpose of the project. Keep the description short.
+
+PROJECT_BRIEF          =
+
+# With the PROJECT_LOGO tag one can specify a logo or an icon that is included
+# in the documentation. The maximum height of the logo should not exceed 55
+# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
+# the logo to the output directory.
+
+PROJECT_LOGO           =
+
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
+# into which the generated documentation will be written. If a relative path is
+# entered, it will be relative to the location where doxygen was started. If
+# left blank the current directory will be used.
+
+OUTPUT_DIRECTORY       = dist
+
+# If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
+# directories (in 2 levels) under the output directory of each output format and
+# will distribute the generated files over these directories. Enabling this
+# option can be useful when feeding doxygen a huge amount of source files, where
+# putting all generated files in the same directory would otherwise causes
+# performance problems for the file system.
+# The default value is: NO.
+
+CREATE_SUBDIRS         = NO
+
+# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
+# characters to appear in the names of generated files. If set to NO, non-ASCII
+# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
+# U+3044.
+# The default value is: NO.
+
+ALLOW_UNICODE_NAMES    = NO
+
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all
+# documentation generated by doxygen is written. Doxygen will use this
+# information to generate all constant output in the proper language.
+# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
+# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
+# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
+# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
+# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
+# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
+# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
+# Ukrainian and Vietnamese.
+# The default value is: English.
+
+OUTPUT_LANGUAGE        = English
+
+# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
+# descriptions after the members that are listed in the file and class
+# documentation (similar to Javadoc). Set to NO to disable this.
+# The default value is: YES.
+
+BRIEF_MEMBER_DESC      = YES
+
+# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
+# description of a member or function before the detailed description
+#
+# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
+# brief descriptions will be completely suppressed.
+# The default value is: YES.
+
+REPEAT_BRIEF           = YES
+
+# This tag implements a quasi-intelligent brief description abbreviator that is
+# used to form the text in various listings. Each string in this list, if found
+# as the leading text of the brief description, will be stripped from the text
+# and the result, after processing the whole list, is used as the annotated
+# text. Otherwise, the brief description is used as-is. If left blank, the
+# following values are used ($name is automatically replaced with the name of
+# the entity):The $name class, The $name widget, The $name file, is, provides,
+# specifies, contains, represents, a, an and the.
+
+ABBREVIATE_BRIEF       = "The $name class" \
+                         "The $name widget" \
+                         "The $name file" \
+                         is \
+                         provides \
+                         specifies \
+                         contains \
+                         represents \
+                         a \
+                         an \
+                         the
+
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
+# doxygen will generate a detailed section even if there is only a brief
+# description.
+# The default value is: NO.
+
+ALWAYS_DETAILED_SEC    = NO
+
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
+# inherited members of a class in the documentation of that class as if those
+# members were ordinary class members. Constructors, destructors and assignment
+# operators of the base classes will not be shown.
+# The default value is: NO.
+
+INLINE_INHERITED_MEMB  = NO
+
+# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
+# before files name in the file list and in the header files. If set to NO the
+# shortest path that makes the file name unique will be used
+# The default value is: YES.
+
+FULL_PATH_NAMES        = YES
+
+# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
+# Stripping is only done if one of the specified strings matches the left-hand
+# part of the path. The tag can be used to show relative paths in the file list.
+# If left blank the directory from which doxygen is run is used as the path to
+# strip.
+#
+# Note that you can specify absolute paths here, but also relative paths, which
+# will be relative from the directory where doxygen is started.
+# This tag requires that the tag FULL_PATH_NAMES is set to YES.
+
+STRIP_FROM_PATH        =
+
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
+# path mentioned in the documentation of a class, which tells the reader which
+# header file to include in order to use a class. If left blank only the name of
+# the header file containing the class definition is used. Otherwise one should
+# specify the list of include paths that are normally passed to the compiler
+# using the -I flag.
+
+STRIP_FROM_INC_PATH    =
+
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
+# less readable) file names. This can be useful is your file systems doesn't
+# support long names like on DOS, Mac, or CD-ROM.
+# The default value is: NO.
+
+SHORT_NAMES            = NO
+
+# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
+# first line (until the first dot) of a Javadoc-style comment as the brief
+# description. If set to NO, the Javadoc-style will behave just like regular Qt-
+# style comments (thus requiring an explicit @brief command for a brief
+# description.)
+# The default value is: NO.
+
+JAVADOC_AUTOBRIEF      = NO
+
+# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
+# such as
+# /***************
+# as being the beginning of a Javadoc-style comment "banner". If set to NO, the
+# Javadoc-style will behave just like regular comments and it will not be
+# interpreted by doxygen.
+# The default value is: NO.
+
+JAVADOC_BANNER         = NO
+
+# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
+# line (until the first dot) of a Qt-style comment as the brief description. If
+# set to NO, the Qt-style will behave just like regular Qt-style comments (thus
+# requiring an explicit \brief command for a brief description.)
+# The default value is: NO.
+
+QT_AUTOBRIEF           = NO
+
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
+# multi-line C++ special comment block (i.e. a block of //! or /// comments) as
+# a brief description. This used to be the default behavior. The new default is
+# to treat a multi-line C++ comment block as a detailed description. Set this
+# tag to YES if you prefer the old behavior instead.
+#
+# Note that setting this tag to YES also means that rational rose comments are
+# not recognized any more.
+# The default value is: NO.
+
+MULTILINE_CPP_IS_BRIEF = NO
+
+# By default Python docstrings are displayed as preformatted text and doxygen's
+# special commands cannot be used. By setting PYTHON_DOCSTRING to NO the
+# doxygen's special commands can be used and the contents of the docstring
+# documentation blocks is shown as doxygen documentation.
+# The default value is: YES.
+
+PYTHON_DOCSTRING       = YES
+
+# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
+# documentation from any documented member that it re-implements.
+# The default value is: YES.
+
+INHERIT_DOCS           = YES
+
+# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
+# page for each member. If set to NO, the documentation of a member will be part
+# of the file/class/namespace that contains it.
+# The default value is: NO.
+
+SEPARATE_MEMBER_PAGES  = NO
+
+# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
+# uses this value to replace tabs by spaces in code fragments.
+# Minimum value: 1, maximum value: 16, default value: 4.
+
+TAB_SIZE               = 4
+
+# This tag can be used to specify a number of aliases that act as commands in
+# the documentation. An alias has the form:
+# name=value
+# For example adding
+# "sideeffect=@par Side Effects:^^"
+# will allow you to put the command \sideeffect (or @sideeffect) in the
+# documentation, which will result in a user-defined paragraph with heading
+# "Side Effects:". Note that you cannot put \n's in the value part of an alias
+# to insert newlines (in the resulting output). You can put ^^ in the value part
+# of an alias to insert a newline as if a physical newline was in the original
+# file. When you need a literal { or } or , in the value part of an alias you
+# have to escape them by means of a backslash (\), this can lead to conflicts
+# with the commands \{ and \} for these it is advised to use the version @{ and
+# @} or use a double escape (\\{ and \\})
+
+ALIASES                =
+
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
+# only. Doxygen will then generate output that is more tailored for C. For
+# instance, some of the names that are used will be different. The list of all
+# members will be omitted, etc.
+# The default value is: NO.
+
+OPTIMIZE_OUTPUT_FOR_C  = NO
+
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
+# Python sources only. Doxygen will then generate output that is more tailored
+# for that language. For instance, namespaces will be presented as packages,
+# qualified scopes will look different, etc.
+# The default value is: NO.
+
+OPTIMIZE_OUTPUT_JAVA   = NO
+
+# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
+# sources. Doxygen will then generate output that is tailored for Fortran.
+# The default value is: NO.
+
+OPTIMIZE_FOR_FORTRAN   = NO
+
+# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
+# sources. Doxygen will then generate output that is tailored for VHDL.
+# The default value is: NO.
+
+OPTIMIZE_OUTPUT_VHDL   = NO
+
+# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
+# sources only. Doxygen will then generate output that is more tailored for that
+# language. For instance, namespaces will be presented as modules, types will be
+# separated into more groups, etc.
+# The default value is: NO.
+
+OPTIMIZE_OUTPUT_SLICE  = NO
+
+# Doxygen selects the parser to use depending on the extension of the files it
+# parses. With this tag you can assign which parser to use for a given
+# extension. Doxygen has a built-in mapping, but you can override or extend it
+# using this tag. The format is ext=language, where ext is a file extension, and
+# language is one of the parsers supported by doxygen: IDL, Java, JavaScript,
+# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,
+# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
+# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
+# tries to guess whether the code is fixed or free formatted code, this is the
+# default for Fortran type files). For instance to make doxygen treat .inc files
+# as Fortran files (default is PHP), and .f files as C (default is Fortran),
+# use: inc=Fortran f=C.
+#
+# Note: For files without extension you can use no_extension as a placeholder.
+#
+# Note that for custom extensions you also need to set FILE_PATTERNS otherwise
+# the files are not read by doxygen. When specifying no_extension you should add
+# * to the FILE_PATTERNS.
+#
+# Note see also the list of default file extension mappings.
+
+EXTENSION_MAPPING      =
+
+# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
+# according to the Markdown format, which allows for more readable
+# documentation. See https://daringfireball.net/projects/markdown/ for details.
+# The output of markdown processing is further processed by doxygen, so you can
+# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
+# case of backward compatibilities issues.
+# The default value is: YES.
+
+MARKDOWN_SUPPORT       = YES
+
+# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
+# to that level are automatically included in the table of contents, even if
+# they do not have an id attribute.
+# Note: This feature currently applies only to Markdown headings.
+# Minimum value: 0, maximum value: 99, default value: 5.
+# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
+
+TOC_INCLUDE_HEADINGS   = 5
+
+# When enabled doxygen tries to link words that correspond to documented
+# classes, or namespaces to their corresponding documentation. Such a link can
+# be prevented in individual cases by putting a % sign in front of the word or
+# globally by setting AUTOLINK_SUPPORT to NO.
+# The default value is: YES.
+
+AUTOLINK_SUPPORT       = YES
+
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
+# to include (a tag file for) the STL sources as input, then you should set this
+# tag to YES in order to let doxygen match functions declarations and
+# definitions whose arguments contain STL classes (e.g. func(std::string);
+# versus func(std::string) {}). This also make the inheritance and collaboration
+# diagrams that involve STL classes more complete and accurate.
+# The default value is: NO.
+
+BUILTIN_STL_SUPPORT    = NO
+
+# If you use Microsoft's C++/CLI language, you should set this option to YES to
+# enable parsing support.
+# The default value is: NO.
+
+CPP_CLI_SUPPORT        = NO
+
+# Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
+# https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen
+# will parse them like normal C++ but will assume all classes use public instead
+# of private inheritance when no explicit protection keyword is present.
+# The default value is: NO.
+
+SIP_SUPPORT            = NO
+
+# For Microsoft's IDL there are propget and propput attributes to indicate
+# getter and setter methods for a property. Setting this option to YES will make
+# doxygen to replace the get and set methods by a property in the documentation.
+# This will only work if the methods are indeed getting or setting a simple
+# type. If this is not the case, or you want to show the methods anyway, you
+# should set this option to NO.
+# The default value is: YES.
+
+IDL_PROPERTY_SUPPORT   = YES
+
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
+# tag is set to YES then doxygen will reuse the documentation of the first
+# member in the group (if any) for the other members of the group. By default
+# all members of a group must be documented explicitly.
+# The default value is: NO.
+
+DISTRIBUTE_GROUP_DOC   = NO
+
+# If one adds a struct or class to a group and this option is enabled, then also
+# any nested class or struct is added to the same group. By default this option
+# is disabled and one has to add nested compounds explicitly via \ingroup.
+# The default value is: NO.
+
+GROUP_NESTED_COMPOUNDS = NO
+
+# Set the SUBGROUPING tag to YES to allow class member groups of the same type
+# (for instance a group of public functions) to be put as a subgroup of that
+# type (e.g. under the Public Functions section). Set it to NO to prevent
+# subgrouping. Alternatively, this can be done per class using the
+# \nosubgrouping command.
+# The default value is: YES.
+
+SUBGROUPING            = YES
+
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
+# are shown inside the group in which they are included (e.g. using \ingroup)
+# instead of on a separate page (for HTML and Man pages) or section (for LaTeX
+# and RTF).
+#
+# Note that this feature does not work in combination with
+# SEPARATE_MEMBER_PAGES.
+# The default value is: NO.
+
+INLINE_GROUPED_CLASSES = NO
+
+# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
+# with only public data fields or simple typedef fields will be shown inline in
+# the documentation of the scope in which they are defined (i.e. file,
+# namespace, or group documentation), provided this scope is documented. If set
+# to NO, structs, classes, and unions are shown on a separate page (for HTML and
+# Man pages) or section (for LaTeX and RTF).
+# The default value is: NO.
+
+INLINE_SIMPLE_STRUCTS  = NO
+
+# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
+# enum is documented as struct, union, or enum with the name of the typedef. So
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
+# with name TypeT. When disabled the typedef will appear as a member of a file,
+# namespace, or class. And the struct will be named TypeS. This can typically be
+# useful for C code in case the coding convention dictates that all compound
+# types are typedef'ed and only the typedef is referenced, never the tag name.
+# The default value is: NO.
+
+TYPEDEF_HIDES_STRUCT   = NO
+
+# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
+# cache is used to resolve symbols given their name and scope. Since this can be
+# an expensive process and often the same symbol appears multiple times in the
+# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
+# doxygen will become slower. If the cache is too large, memory is wasted. The
+# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
+# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
+# symbols. At the end of a run doxygen will report the cache usage and suggest
+# the optimal cache size from a speed point of view.
+# Minimum value: 0, maximum value: 9, default value: 0.
+
+LOOKUP_CACHE_SIZE      = 0
+
+# The NUM_PROC_THREADS specifies the number threads doxygen is allowed to use
+# during processing. When set to 0 doxygen will based this on the number of
+# cores available in the system. You can set it explicitly to a value larger
+# than 0 to get more control over the balance between CPU load and processing
+# speed. At this moment only the input processing can be done using multiple
+# threads. Since this is still an experimental feature the default is set to 1,
+# which effectively disables parallel processing. Please report any issues you
+# encounter. Generating dot graphs in parallel is controlled by the
+# DOT_NUM_THREADS setting.
+# Minimum value: 0, maximum value: 32, default value: 1.
+
+NUM_PROC_THREADS       = 1
+
+#---------------------------------------------------------------------------
+# Build related configuration options
+#---------------------------------------------------------------------------
+
+# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
+# documentation are documented, even if no documentation was available. Private
+# class members and static file members will be hidden unless the
+# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
+# Note: This will also disable the warnings about undocumented members that are
+# normally produced when WARNINGS is set to YES.
+# The default value is: NO.
+
+EXTRACT_ALL            = NO
+
+# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
+# be included in the documentation.
+# The default value is: NO.
+
+EXTRACT_PRIVATE        = NO
+
+# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual
+# methods of a class will be included in the documentation.
+# The default value is: NO.
+
+EXTRACT_PRIV_VIRTUAL   = NO
+
+# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
+# scope will be included in the documentation.
+# The default value is: NO.
+
+EXTRACT_PACKAGE        = NO
+
+# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
+# included in the documentation.
+# The default value is: NO.
+
+EXTRACT_STATIC         = NO
+
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined
+# locally in source files will be included in the documentation. If set to NO,
+# only classes defined in header files are included. Does not have any effect
+# for Java sources.
+# The default value is: YES.
+
+EXTRACT_LOCAL_CLASSES  = YES
+
+# This flag is only useful for Objective-C code. If set to YES, local methods,
+# which are defined in the implementation section but not in the interface are
+# included in the documentation. If set to NO, only methods in the interface are
+# included.
+# The default value is: NO.
+
+EXTRACT_LOCAL_METHODS  = NO
+
+# If this flag is set to YES, the members of anonymous namespaces will be
+# extracted and appear in the documentation as a namespace called
+# 'anonymous_namespace{file}', where file will be replaced with the base name of
+# the file that contains the anonymous namespace. By default anonymous namespace
+# are hidden.
+# The default value is: NO.
+
+EXTRACT_ANON_NSPACES   = NO
+
+# If this flag is set to YES, the name of an unnamed parameter in a declaration
+# will be determined by the corresponding definition. By default unnamed
+# parameters remain unnamed in the output.
+# The default value is: YES.
+
+RESOLVE_UNNAMED_PARAMS = YES
+
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
+# undocumented members inside documented classes or files. If set to NO these
+# members will be included in the various overviews, but no documentation
+# section is generated. This option has no effect if EXTRACT_ALL is enabled.
+# The default value is: NO.
+
+HIDE_UNDOC_MEMBERS     = NO
+
+# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
+# undocumented classes that are normally visible in the class hierarchy. If set
+# to NO, these classes will be included in the various overviews. This option
+# has no effect if EXTRACT_ALL is enabled.
+# The default value is: NO.
+
+HIDE_UNDOC_CLASSES     = NO
+
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
+# declarations. If set to NO, these declarations will be included in the
+# documentation.
+# The default value is: NO.
+
+HIDE_FRIEND_COMPOUNDS  = NO
+
+# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
+# documentation blocks found inside the body of a function. If set to NO, these
+# blocks will be appended to the function's detailed documentation block.
+# The default value is: NO.
+
+HIDE_IN_BODY_DOCS      = NO
+
+# The INTERNAL_DOCS tag determines if documentation that is typed after a
+# \internal command is included. If the tag is set to NO then the documentation
+# will be excluded. Set it to YES to include the internal documentation.
+# The default value is: NO.
+
+INTERNAL_DOCS          = NO
+
+# With the correct setting of option CASE_SENSE_NAMES doxygen will better be
+# able to match the capabilities of the underlying filesystem. In case the
+# filesystem is case sensitive (i.e. it supports files in the same directory
+# whose names only differ in casing), the option must be set to YES to properly
+# deal with such files in case they appear in the input. For filesystems that
+# are not case sensitive the option should be be set to NO to properly deal with
+# output files written for symbols that only differ in casing, such as for two
+# classes, one named CLASS and the other named Class, and to also support
+# references to files without having to specify the exact matching casing. On
+# Windows (including Cygwin) and MacOS, users should typically set this option
+# to NO, whereas on Linux or other Unix flavors it should typically be set to
+# YES.
+# The default value is: system dependent.
+
+CASE_SENSE_NAMES       = YES
+
+# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
+# their full class and namespace scopes in the documentation. If set to YES, the
+# scope will be hidden.
+# The default value is: NO.
+
+HIDE_SCOPE_NAMES       = NO
+
+# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will
+# append additional text to a page's title, such as Class Reference. If set to
+# YES the compound reference will be hidden.
+# The default value is: NO.
+
+HIDE_COMPOUND_REFERENCE= NO
+
+# If the SHOW_HEADERFILE tag is set to YES then the documentation for a class
+# will show which file needs to be included to use the class.
+# The default value is: YES.
+
+SHOW_HEADERFILE        = YES
+
+# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
+# the files that are included by a file in the documentation of that file.
+# The default value is: YES.
+
+SHOW_INCLUDE_FILES     = YES
+
+# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
+# grouped member an include statement to the documentation, telling the reader
+# which file to include in order to use the member.
+# The default value is: NO.
+
+SHOW_GROUPED_MEMB_INC  = NO
+
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
+# files with double quotes in the documentation rather than with sharp brackets.
+# The default value is: NO.
+
+FORCE_LOCAL_INCLUDES   = NO
+
+# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
+# documentation for inline members.
+# The default value is: YES.
+
+INLINE_INFO            = YES
+
+# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
+# (detailed) documentation of file and class members alphabetically by member
+# name. If set to NO, the members will appear in declaration order.
+# The default value is: YES.
+
+SORT_MEMBER_DOCS       = YES
+
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
+# descriptions of file, namespace and class members alphabetically by member
+# name. If set to NO, the members will appear in declaration order. Note that
+# this will also influence the order of the classes in the class list.
+# The default value is: NO.
+
+SORT_BRIEF_DOCS        = NO
+
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
+# (brief and detailed) documentation of class members so that constructors and
+# destructors are listed first. If set to NO the constructors will appear in the
+# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
+# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
+# member documentation.
+# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
+# detailed member documentation.
+# The default value is: NO.
+
+SORT_MEMBERS_CTORS_1ST = NO
+
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
+# of group names into alphabetical order. If set to NO the group names will
+# appear in their defined order.
+# The default value is: NO.
+
+SORT_GROUP_NAMES       = NO
+
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
+# fully-qualified names, including namespaces. If set to NO, the class list will
+# be sorted only by class name, not including the namespace part.
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
+# Note: This option applies only to the class list, not to the alphabetical
+# list.
+# The default value is: NO.
+
+SORT_BY_SCOPE_NAME     = NO
+
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
+# type resolution of all parameters of a function it will reject a match between
+# the prototype and the implementation of a member function even if there is
+# only one candidate or it is obvious which candidate to choose by doing a
+# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
+# accept a match between prototype and implementation in such cases.
+# The default value is: NO.
+
+STRICT_PROTO_MATCHING  = NO
+
+# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
+# list. This list is created by putting \todo commands in the documentation.
+# The default value is: YES.
+
+GENERATE_TODOLIST      = YES
+
+# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
+# list. This list is created by putting \test commands in the documentation.
+# The default value is: YES.
+
+GENERATE_TESTLIST      = YES
+
+# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
+# list. This list is created by putting \bug commands in the documentation.
+# The default value is: YES.
+
+GENERATE_BUGLIST       = YES
+
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
+# the deprecated list. This list is created by putting \deprecated commands in
+# the documentation.
+# The default value is: YES.
+
+GENERATE_DEPRECATEDLIST= YES
+
+# The ENABLED_SECTIONS tag can be used to enable conditional documentation
+# sections, marked by \if <section_label> ... \endif and \cond <section_label>
+# ... \endcond blocks.
+
+ENABLED_SECTIONS       =
+
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
+# initial value of a variable or macro / define can have for it to appear in the
+# documentation. If the initializer consists of more lines than specified here
+# it will be hidden. Use a value of 0 to hide initializers completely. The
+# appearance of the value of individual variables and macros / defines can be
+# controlled using \showinitializer or \hideinitializer command in the
+# documentation regardless of this setting.
+# Minimum value: 0, maximum value: 10000, default value: 30.
+
+MAX_INITIALIZER_LINES  = 30
+
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
+# the bottom of the documentation of classes and structs. If set to YES, the
+# list will mention the files that were used to generate the documentation.
+# The default value is: YES.
+
+SHOW_USED_FILES        = YES
+
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
+# will remove the Files entry from the Quick Index and from the Folder Tree View
+# (if specified).
+# The default value is: YES.
+
+SHOW_FILES             = YES
+
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
+# page. This will remove the Namespaces entry from the Quick Index and from the
+# Folder Tree View (if specified).
+# The default value is: YES.
+
+SHOW_NAMESPACES        = YES
+
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that
+# doxygen should invoke to get the current version for each file (typically from
+# the version control system). Doxygen will invoke the program by executing (via
+# popen()) the command command input-file, where command is the value of the
+# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
+# by doxygen. Whatever the program writes to standard output is used as the file
+# version. For an example see the documentation.
+
+FILE_VERSION_FILTER    =
+
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
+# by doxygen. The layout file controls the global structure of the generated
+# output files in an output format independent way. To create the layout file
+# that represents doxygen's defaults, run doxygen with the -l option. You can
+# optionally specify a file name after the option, if omitted DoxygenLayout.xml
+# will be used as the name of the layout file. See also section "Changing the
+# layout of pages" for information.
+#
+# Note that if you run doxygen from a directory containing a file called
+# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
+# tag is left empty.
+
+LAYOUT_FILE            =
+
+# The CITE_BIB_FILES tag can be used to specify one or more bib files containing
+# the reference definitions. This must be a list of .bib files. The .bib
+# extension is automatically appended if omitted. This requires the bibtex tool
+# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.
+# For LaTeX the style of the bibliography can be controlled using
+# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
+# search path. See also \cite for info how to create references.
+
+CITE_BIB_FILES         =
+
+#---------------------------------------------------------------------------
+# Configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+
+# The QUIET tag can be used to turn on/off the messages that are generated to
+# standard output by doxygen. If QUIET is set to YES this implies that the
+# messages are off.
+# The default value is: NO.
+
+QUIET                  = NO
+
+# The WARNINGS tag can be used to turn on/off the warning messages that are
+# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
+# this implies that the warnings are on.
+#
+# Tip: Turn warnings on while writing the documentation.
+# The default value is: YES.
+
+WARNINGS               = YES
+
+# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
+# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
+# will automatically be disabled.
+# The default value is: YES.
+
+WARN_IF_UNDOCUMENTED   = YES
+
+# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
+# potential errors in the documentation, such as documenting some parameters in
+# a documented function twice, or documenting parameters that don't exist or
+# using markup commands wrongly.
+# The default value is: YES.
+
+WARN_IF_DOC_ERROR      = YES
+
+# If WARN_IF_INCOMPLETE_DOC is set to YES, doxygen will warn about incomplete
+# function parameter documentation. If set to NO, doxygen will accept that some
+# parameters have no documentation without warning.
+# The default value is: YES.
+
+WARN_IF_INCOMPLETE_DOC = YES
+
+# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
+# are documented, but have no documentation for their parameters or return
+# value. If set to NO, doxygen will only warn about wrong parameter
+# documentation, but not about the absence of documentation. If EXTRACT_ALL is
+# set to YES then this flag will automatically be disabled. See also
+# WARN_IF_INCOMPLETE_DOC
+# The default value is: NO.
+
+WARN_NO_PARAMDOC       = NO
+
+# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when
+# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS
+# then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but
+# at the end of the doxygen process doxygen will return with a non-zero status.
+# Possible values are: NO, YES and FAIL_ON_WARNINGS.
+# The default value is: NO.
+
+WARN_AS_ERROR          = NO
+
+# The WARN_FORMAT tag determines the format of the warning messages that doxygen
+# can produce. The string should contain the $file, $line, and $text tags, which
+# will be replaced by the file and line number from which the warning originated
+# and the warning text. Optionally the format may contain $version, which will
+# be replaced by the version of the file (if it could be obtained via
+# FILE_VERSION_FILTER)
+# The default value is: $file:$line: $text.
+
+WARN_FORMAT            = "$file:$line: $text"
+
+# The WARN_LOGFILE tag can be used to specify a file to which warning and error
+# messages should be written. If left blank the output is written to standard
+# error (stderr). In case the file specified cannot be opened for writing the
+# warning and error messages are written to standard error. When as file - is
+# specified the warning and error messages are written to standard output
+# (stdout).
+
+WARN_LOGFILE           =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the input files
+#---------------------------------------------------------------------------
+
+# The INPUT tag is used to specify the files and/or directories that contain
+# documented source files. You may enter file names like myfile.cpp or
+# directories like /usr/src/myproject. Separate the files or directories with
+# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
+# Note: If this tag is empty the current directory is searched.
+
+INPUT                  = ../include \
+                         src/index.dox \
+                         src/get_started.dox \
+                         src/development.dox
+
+# This tag can be used to specify the character encoding of the source files
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
+# libiconv (or the iconv built into libc) for the transcoding. See the libiconv
+# documentation (see:
+# https://www.gnu.org/software/libiconv/) for the list of possible encodings.
+# The default value is: UTF-8.
+
+INPUT_ENCODING         = UTF-8
+
+# If the value of the INPUT tag contains directories, you can use the
+# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
+# *.h) to filter out the source-files in the directories.
+#
+# Note that for custom extensions or not directly supported extensions you also
+# need to set EXTENSION_MAPPING for the extension otherwise the files are not
+# read by doxygen.
+#
+# Note the list of default checked file patterns might differ from the list of
+# default file extension mappings.
+#
+# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
+# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
+# *.hh, *.hxx, *.hpp, *.h++, *.l, *.cs, *.d, *.php, *.php4, *.php5, *.phtml,
+# *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to be provided as doxygen C
+# comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f18, *.f, *.for, *.vhd,
+# *.vhdl, *.ucf, *.qsf and *.ice.
+
+FILE_PATTERNS          = *.c \
+                         *.cc \
+                         *.cxx \
+                         *.cpp \
+                         *.c++ \
+                         *.java \
+                         *.ii \
+                         *.ixx \
+                         *.ipp \
+                         *.i++ \
+                         *.inl \
+                         *.idl \
+                         *.ddl \
+                         *.odl \
+                         *.h \
+                         *.hh \
+                         *.hxx \
+                         *.hpp \
+                         *.h++ \
+                         *.l \
+                         *.cs \
+                         *.d \
+                         *.php \
+                         *.php4 \
+                         *.php5 \
+                         *.phtml \
+                         *.inc \
+                         *.m \
+                         *.markdown \
+                         *.md \
+                         *.mm \
+                         *.dox \
+                         *.py \
+                         *.pyw \
+                         *.f90 \
+                         *.f95 \
+                         *.f03 \
+                         *.f08 \
+                         *.f18 \
+                         *.f \
+                         *.for \
+                         *.vhd \
+                         *.vhdl \
+                         *.ucf \
+                         *.qsf \
+                         *.ice
+
+# The RECURSIVE tag can be used to specify whether or not subdirectories should
+# be searched for input files as well.
+# The default value is: NO.
+
+RECURSIVE              = NO
+
+# The EXCLUDE tag can be used to specify files and/or directories that should be
+# excluded from the INPUT source files. This way you can easily exclude a
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
+#
+# Note that relative paths are relative to the directory from which doxygen is
+# run.
+
+EXCLUDE                =
+
+# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
+# directories that are symbolic links (a Unix file system feature) are excluded
+# from the input.
+# The default value is: NO.
+
+EXCLUDE_SYMLINKS       = NO
+
+# If the value of the INPUT tag contains directories, you can use the
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
+# certain files from those directories.
+#
+# Note that the wildcards are matched against the file with absolute path, so to
+# exclude all test directories for example use the pattern */test/*
+
+EXCLUDE_PATTERNS       =
+
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
+# (namespaces, classes, functions, etc.) that should be excluded from the
+# output. The symbol name can be a fully qualified name, a word, or if the
+# wildcard * is used, a substring. Examples: ANamespace, AClass,
+# ANamespace::AClass, ANamespace::*Test
+#
+# Note that the wildcards are matched against the file with absolute path, so to
+# exclude all test directories use the pattern */test/*
+
+EXCLUDE_SYMBOLS        =
+
+# The EXAMPLE_PATH tag can be used to specify one or more files or directories
+# that contain example code fragments that are included (see the \include
+# command).
+
+EXAMPLE_PATH           = ../examples/c ../examples/cxx
+
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
+# *.h) to filter out the source-files in the directories. If left blank all
+# files are included.
+
+EXAMPLE_PATTERNS       = *
+
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
+# searched for input files to be used with the \include or \dontinclude commands
+# irrespective of the value of the RECURSIVE tag.
+# The default value is: NO.
+
+EXAMPLE_RECURSIVE      = NO
+
+# The IMAGE_PATH tag can be used to specify one or more files or directories
+# that contain images that are to be included in the documentation (see the
+# \image command).
+
+IMAGE_PATH             =
+
+# The INPUT_FILTER tag can be used to specify a program that doxygen should
+# invoke to filter for each input file. Doxygen will invoke the filter program
+# by executing (via popen()) the command:
+#
+# <filter> <input-file>
+#
+# where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
+# name of an input file. Doxygen will then use the output that the filter
+# program writes to standard output. If FILTER_PATTERNS is specified, this tag
+# will be ignored.
+#
+# Note that the filter must not add or remove lines; it is applied before the
+# code is scanned, but not when the output code is generated. If lines are added
+# or removed, the anchors will not be placed correctly.
+#
+# Note that for custom extensions or not directly supported extensions you also
+# need to set EXTENSION_MAPPING for the extension otherwise the files are not
+# properly processed by doxygen.
+
+INPUT_FILTER           =
+
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
+# basis. Doxygen will compare the file name with each pattern and apply the
+# filter if there is a match. The filters are a list of the form: pattern=filter
+# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
+# filters are used. If the FILTER_PATTERNS tag is empty or if none of the
+# patterns match the file name, INPUT_FILTER is applied.
+#
+# Note that for custom extensions or not directly supported extensions you also
+# need to set EXTENSION_MAPPING for the extension otherwise the files are not
+# properly processed by doxygen.
+
+FILTER_PATTERNS        =
+
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
+# INPUT_FILTER) will also be used to filter the input files that are used for
+# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
+# The default value is: NO.
+
+FILTER_SOURCE_FILES    = NO
+
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
+# it is also possible to disable source filtering for a specific pattern using
+# *.ext= (so without naming a filter).
+# This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
+
+FILTER_SOURCE_PATTERNS =
+
+# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
+# is part of the input, its contents will be placed on the main page
+# (index.html). This can be useful if you have a project on for instance GitHub
+# and want to reuse the introduction page also for the doxygen output.
+
+USE_MDFILE_AS_MAINPAGE =
+
+#---------------------------------------------------------------------------
+# Configuration options related to source browsing
+#---------------------------------------------------------------------------
+
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will be
+# generated. Documented entities will be cross-referenced with these sources.
+#
+# Note: To get rid of all source code in the generated output, make sure that
+# also VERBATIM_HEADERS is set to NO.
+# The default value is: NO.
+
+SOURCE_BROWSER         = NO
+
+# Setting the INLINE_SOURCES tag to YES will include the body of functions,
+# classes and enums directly into the documentation.
+# The default value is: NO.
+
+INLINE_SOURCES         = NO
+
+# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
+# special comment blocks from generated source code fragments. Normal C, C++ and
+# Fortran comments will always remain visible.
+# The default value is: YES.
+
+STRIP_CODE_COMMENTS    = YES
+
+# If the REFERENCED_BY_RELATION tag is set to YES then for each documented
+# entity all documented functions referencing it will be listed.
+# The default value is: NO.
+
+REFERENCED_BY_RELATION = NO
+
+# If the REFERENCES_RELATION tag is set to YES then for each documented function
+# all documented entities called/used by that function will be listed.
+# The default value is: NO.
+
+REFERENCES_RELATION    = NO
+
+# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
+# to YES then the hyperlinks from functions in REFERENCES_RELATION and
+# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
+# link to the documentation.
+# The default value is: YES.
+
+REFERENCES_LINK_SOURCE = YES
+
+# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
+# source code will show a tooltip with additional information such as prototype,
+# brief description and links to the definition and documentation. Since this
+# will make the HTML file larger and loading of large files a bit slower, you
+# can opt to disable this feature.
+# The default value is: YES.
+# This tag requires that the tag SOURCE_BROWSER is set to YES.
+
+SOURCE_TOOLTIPS        = YES
+
+# If the USE_HTAGS tag is set to YES then the references to source code will
+# point to the HTML generated by the htags(1) tool instead of doxygen built-in
+# source browser. The htags tool is part of GNU's global source tagging system
+# (see https://www.gnu.org/software/global/global.html). You will need version
+# 4.8.6 or higher.
+#
+# To use it do the following:
+# - Install the latest version of global
+# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
+# - Make sure the INPUT points to the root of the source tree
+# - Run doxygen as normal
+#
+# Doxygen will invoke htags (and that will in turn invoke gtags), so these
+# tools must be available from the command line (i.e. in the search path).
+#
+# The result: instead of the source browser generated by doxygen, the links to
+# source code will now point to the output of htags.
+# The default value is: NO.
+# This tag requires that the tag SOURCE_BROWSER is set to YES.
+
+USE_HTAGS              = NO
+
+# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
+# verbatim copy of the header file for each class for which an include is
+# specified. Set to NO to disable this.
+# See also: Section \class.
+# The default value is: YES.
+
+VERBATIM_HEADERS       = YES
+
+#---------------------------------------------------------------------------
+# Configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
+# compounds will be generated. Enable this if the project contains a lot of
+# classes, structs, unions or interfaces.
+# The default value is: YES.
+
+ALPHABETICAL_INDEX     = YES
+
+# In case all classes in a project start with a common prefix, all classes will
+# be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
+# can be used to specify a prefix (or a list of prefixes) that should be ignored
+# while generating the index headers.
+# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
+
+IGNORE_PREFIX          =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the HTML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
+# The default value is: YES.
+
+GENERATE_HTML          = YES
+
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
+# it.
+# The default directory is: html.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_OUTPUT            = html
+
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
+# generated HTML page (for example: .htm, .php, .asp).
+# The default value is: .html.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_FILE_EXTENSION    = .html
+
+# The HTML_HEADER tag can be used to specify a user-defined HTML header file for
+# each generated HTML page. If the tag is left blank doxygen will generate a
+# standard header.
+#
+# To get valid HTML the header file that includes any scripts and style sheets
+# that doxygen needs, which is dependent on the configuration options used (e.g.
+# the setting GENERATE_TREEVIEW). It is highly recommended to start with a
+# default header using
+# doxygen -w html new_header.html new_footer.html new_stylesheet.css
+# YourConfigFile
+# and then modify the file new_header.html. See also section "Doxygen usage"
+# for information on how to generate the default header that doxygen normally
+# uses.
+# Note: The header is subject to change so you typically have to regenerate the
+# default header when upgrading to a newer version of doxygen. For a description
+# of the possible markers and block names see the documentation.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_HEADER            =
+
+# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
+# generated HTML page. If the tag is left blank doxygen will generate a standard
+# footer. See HTML_HEADER for more information on how to generate a default
+# footer and what special commands can be used inside the footer. See also
+# section "Doxygen usage" for information on how to generate the default footer
+# that doxygen normally uses.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_FOOTER            =
+
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
+# sheet that is used by each HTML page. It can be used to fine-tune the look of
+# the HTML output. If left blank doxygen will generate a default style sheet.
+# See also section "Doxygen usage" for information on how to generate the style
+# sheet that doxygen normally uses.
+# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
+# it is more robust and this tag (HTML_STYLESHEET) will in the future become
+# obsolete.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_STYLESHEET        =
+
+# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
+# cascading style sheets that are included after the standard style sheets
+# created by doxygen. Using this option one can overrule certain style aspects.
+# This is preferred over using HTML_STYLESHEET since it does not replace the
+# standard style sheet and is therefore more robust against future updates.
+# Doxygen will copy the style sheet files to the output directory.
+# Note: The order of the extra style sheet files is of importance (e.g. the last
+# style sheet in the list overrules the setting of the previous ones in the
+# list). For an example see the documentation.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_EXTRA_STYLESHEET  =
+
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
+# other source files which should be copied to the HTML output directory. Note
+# that these files will be copied to the base HTML output directory. Use the
+# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that the
+# files will be copied as-is; there are no commands or markers available.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_EXTRA_FILES       =
+
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
+# will adjust the colors in the style sheet and background images according to
+# this color. Hue is specified as an angle on a color-wheel, see
+# https://en.wikipedia.org/wiki/Hue for more information. For instance the value
+# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
+# purple, and 360 is red again.
+# Minimum value: 0, maximum value: 359, default value: 220.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_COLORSTYLE_HUE    = 220
+
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
+# in the HTML output. For a value of 0 the output will use gray-scales only. A
+# value of 255 will produce the most vivid colors.
+# Minimum value: 0, maximum value: 255, default value: 100.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_COLORSTYLE_SAT    = 100
+
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
+# luminance component of the colors in the HTML output. Values below 100
+# gradually make the output lighter, whereas values above 100 make the output
+# darker. The value divided by 100 is the actual gamma applied, so 80 represents
+# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
+# change the gamma.
+# Minimum value: 40, maximum value: 240, default value: 80.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_COLORSTYLE_GAMMA  = 80
+
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
+# page will contain the date and time when the page was generated. Setting this
+# to YES can help to show when doxygen was last run and thus if the
+# documentation is up to date.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_TIMESTAMP         = NO
+
+# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML
+# documentation will contain a main index with vertical navigation menus that
+# are dynamically created via JavaScript. If disabled, the navigation index will
+# consists of multiple levels of tabs that are statically embedded in every HTML
+# page. Disable this option to support browsers that do not have JavaScript,
+# like the Qt help browser.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_DYNAMIC_MENUS     = YES
+
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
+# documentation will contain sections that can be hidden and shown after the
+# page has loaded.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_DYNAMIC_SECTIONS  = NO
+
+# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
+# shown in the various tree structured indices initially; the user can expand
+# and collapse entries dynamically later on. Doxygen will expand the tree to
+# such a level that at most the specified number of entries are visible (unless
+# a fully collapsed tree already exceeds this amount). So setting the number of
+# entries 1 will produce a full collapsed tree by default. 0 is a special value
+# representing an infinite number of entries and will result in a full expanded
+# tree by default.
+# Minimum value: 0, maximum value: 9999, default value: 100.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_INDEX_NUM_ENTRIES = 100
+
+# If the GENERATE_DOCSET tag is set to YES, additional index files will be
+# generated that can be used as input for Apple's Xcode 3 integrated development
+# environment (see:
+# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To
+# create a documentation set, doxygen will generate a Makefile in the HTML
+# output directory. Running make will produce the docset in that directory and
+# running make install will install the docset in
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
+# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
+# genXcode/_index.html for more information.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+GENERATE_DOCSET        = NO
+
+# This tag determines the name of the docset feed. A documentation feed provides
+# an umbrella under which multiple documentation sets from a single provider
+# (such as a company or product suite) can be grouped.
+# The default value is: Doxygen generated docs.
+# This tag requires that the tag GENERATE_DOCSET is set to YES.
+
+DOCSET_FEEDNAME        = "Doxygen generated docs"
+
+# This tag determines the URL of the docset feed. A documentation feed provides
+# an umbrella under which multiple documentation sets from a single provider
+# (such as a company or product suite) can be grouped.
+# This tag requires that the tag GENERATE_DOCSET is set to YES.
+
+DOCSET_FEEDURL         =
+
+# This tag specifies a string that should uniquely identify the documentation
+# set bundle. This should be a reverse domain-name style string, e.g.
+# com.mycompany.MyDocSet. Doxygen will append .docset to the name.
+# The default value is: org.doxygen.Project.
+# This tag requires that the tag GENERATE_DOCSET is set to YES.
+
+DOCSET_BUNDLE_ID       = org.doxygen.Project
+
+# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
+# the documentation publisher. This should be a reverse domain-name style
+# string, e.g. com.mycompany.MyDocSet.documentation.
+# The default value is: org.doxygen.Publisher.
+# This tag requires that the tag GENERATE_DOCSET is set to YES.
+
+DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
+
+# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
+# The default value is: Publisher.
+# This tag requires that the tag GENERATE_DOCSET is set to YES.
+
+DOCSET_PUBLISHER_NAME  = Publisher
+
+# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
+# additional HTML index files: index.hhp, index.hhc, and index.hhk. The
+# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
+# on Windows. In the beginning of 2021 Microsoft took the original page, with
+# a.o. the download links, offline the HTML help workshop was already many years
+# in maintenance mode). You can download the HTML help workshop from the web
+# archives at Installation executable (see:
+# http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo
+# ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).
+#
+# The HTML Help Workshop contains a compiler that can convert all HTML output
+# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
+# files are now used as the Windows 98 help format, and will replace the old
+# Windows help format (.hlp) on all Windows platforms in the future. Compressed
+# HTML files also contain an index, a table of contents, and you can search for
+# words in the documentation. The HTML workshop also contains a viewer for
+# compressed HTML files.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+GENERATE_HTMLHELP      = NO
+
+# The CHM_FILE tag can be used to specify the file name of the resulting .chm
+# file. You can add a path in front of the file if the result should not be
+# written to the html output directory.
+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
+
+CHM_FILE               =
+
+# The HHC_LOCATION tag can be used to specify the location (absolute path
+# including file name) of the HTML help compiler (hhc.exe). If non-empty,
+# doxygen will try to run the HTML help compiler on the generated index.hhp.
+# The file has to be specified with full path.
+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
+
+HHC_LOCATION           =
+
+# The GENERATE_CHI flag controls if a separate .chi index file is generated
+# (YES) or that it should be included in the main .chm file (NO).
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
+
+GENERATE_CHI           = NO
+
+# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)
+# and project file content.
+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
+
+CHM_INDEX_ENCODING     =
+
+# The BINARY_TOC flag controls whether a binary table of contents is generated
+# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
+# enables the Previous and Next buttons.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
+
+BINARY_TOC             = NO
+
+# The TOC_EXPAND flag can be set to YES to add extra items for group members to
+# the table of contents of the HTML help documentation and to the tree view.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
+
+TOC_EXPAND             = NO
+
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
+# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
+# (.qch) of the generated HTML documentation.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+GENERATE_QHP           = NO
+
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
+# the file name of the resulting .qch file. The path specified is relative to
+# the HTML output folder.
+# This tag requires that the tag GENERATE_QHP is set to YES.
+
+QCH_FILE               =
+
+# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
+# Project output. For more information please see Qt Help Project / Namespace
+# (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
+# The default value is: org.doxygen.Project.
+# This tag requires that the tag GENERATE_QHP is set to YES.
+
+QHP_NAMESPACE          = org.doxygen.Project
+
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
+# Help Project output. For more information please see Qt Help Project / Virtual
+# Folders (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).
+# The default value is: doc.
+# This tag requires that the tag GENERATE_QHP is set to YES.
+
+QHP_VIRTUAL_FOLDER     = doc
+
+# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
+# filter to add. For more information please see Qt Help Project / Custom
+# Filters (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
+# This tag requires that the tag GENERATE_QHP is set to YES.
+
+QHP_CUST_FILTER_NAME   =
+
+# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
+# custom filter to add. For more information please see Qt Help Project / Custom
+# Filters (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
+# This tag requires that the tag GENERATE_QHP is set to YES.
+
+QHP_CUST_FILTER_ATTRS  =
+
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
+# project's filter section matches. Qt Help Project / Filter Attributes (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
+# This tag requires that the tag GENERATE_QHP is set to YES.
+
+QHP_SECT_FILTER_ATTRS  =
+
+# The QHG_LOCATION tag can be used to specify the location (absolute path
+# including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to
+# run qhelpgenerator on the generated .qhp file.
+# This tag requires that the tag GENERATE_QHP is set to YES.
+
+QHG_LOCATION           =
+
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
+# generated, together with the HTML files, they form an Eclipse help plugin. To
+# install this plugin and make it available under the help contents menu in
+# Eclipse, the contents of the directory containing the HTML and XML files needs
+# to be copied into the plugins directory of eclipse. The name of the directory
+# within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
+# After copying Eclipse needs to be restarted before the help appears.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+GENERATE_ECLIPSEHELP   = NO
+
+# A unique identifier for the Eclipse help plugin. When installing the plugin
+# the directory name containing the HTML and XML files should also have this
+# name. Each documentation set should have its own identifier.
+# The default value is: org.doxygen.Project.
+# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
+
+ECLIPSE_DOC_ID         = org.doxygen.Project
+
+# If you want full control over the layout of the generated HTML pages it might
+# be necessary to disable the index and replace it with your own. The
+# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
+# of each HTML page. A value of NO enables the index and the value YES disables
+# it. Since the tabs in the index contain the same information as the navigation
+# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+DISABLE_INDEX          = NO
+
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
+# structure should be generated to display hierarchical information. If the tag
+# value is set to YES, a side panel will be generated containing a tree-like
+# index structure (just like the one that is generated for HTML Help). For this
+# to work a browser that supports JavaScript, DHTML, CSS and frames is required
+# (i.e. any modern browser). Windows users are probably better off using the
+# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
+# further fine tune the look of the index (see "Fine-tuning the output"). As an
+# example, the default style sheet generated by doxygen has an example that
+# shows how to put an image at the root of the tree instead of the PROJECT_NAME.
+# Since the tree basically has the same information as the tab index, you could
+# consider setting DISABLE_INDEX to YES when enabling this option.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+GENERATE_TREEVIEW      = NO
+
+# When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the
+# FULL_SIDEBAR option determines if the side bar is limited to only the treeview
+# area (value NO) or if it should extend to the full height of the window (value
+# YES). Setting this to YES gives a layout similar to
+# https://docs.readthedocs.io with more room for contents, but less room for the
+# project logo, title, and description. If either GENERATE_TREEVIEW or
+# DISABLE_INDEX is set to NO, this option has no effect.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+FULL_SIDEBAR           = NO
+
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
+# doxygen will group on one line in the generated HTML documentation.
+#
+# Note that a value of 0 will completely suppress the enum values from appearing
+# in the overview section.
+# Minimum value: 0, maximum value: 20, default value: 4.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+ENUM_VALUES_PER_LINE   = 4
+
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
+# to set the initial width (in pixels) of the frame in which the tree is shown.
+# Minimum value: 0, maximum value: 1500, default value: 250.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+TREEVIEW_WIDTH         = 250
+
+# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to
+# external symbols imported via tag files in a separate window.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+EXT_LINKS_IN_WINDOW    = NO
+
+# If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email
+# addresses.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+OBFUSCATE_EMAILS       = YES
+
+# If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg
+# tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see
+# https://inkscape.org) to generate formulas as SVG images instead of PNGs for
+# the HTML output. These images will generally look nicer at scaled resolutions.
+# Possible values are: png (the default) and svg (looks nicer but requires the
+# pdf2svg or inkscape tool).
+# The default value is: png.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_FORMULA_FORMAT    = png
+
+# Use this tag to change the font size of LaTeX formulas included as images in
+# the HTML documentation. When you change the font size after a successful
+# doxygen run you need to manually remove any form_*.png images from the HTML
+# output directory to force them to be regenerated.
+# Minimum value: 8, maximum value: 50, default value: 10.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+FORMULA_FONTSIZE       = 10
+
+# Use the FORMULA_TRANSPARENT tag to determine whether or not the images
+# generated for formulas are transparent PNGs. Transparent PNGs are not
+# supported properly for IE 6.0, but are supported on all modern browsers.
+#
+# Note that when changing this option you need to delete any form_*.png files in
+# the HTML output directory before the changes have effect.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+FORMULA_TRANSPARENT    = YES
+
+# The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands
+# to create new LaTeX commands to be used in formulas as building blocks. See
+# the section "Including formulas" for details.
+
+FORMULA_MACROFILE      =
+
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
+# https://www.mathjax.org) which uses client side JavaScript for the rendering
+# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
+# installed or if you want to formulas look prettier in the HTML output. When
+# enabled you may also need to install MathJax separately and configure the path
+# to it using the MATHJAX_RELPATH option.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+USE_MATHJAX            = NO
+
+# With MATHJAX_VERSION it is possible to specify the MathJax version to be used.
+# Note that the different versions of MathJax have different requirements with
+# regards to the different settings, so it is possible that also other MathJax
+# settings have to be changed when switching between the different MathJax
+# versions.
+# Possible values are: MathJax_2 and MathJax_3.
+# The default value is: MathJax_2.
+# This tag requires that the tag USE_MATHJAX is set to YES.
+
+MATHJAX_VERSION        = MathJax_2
+
+# When MathJax is enabled you can set the default output format to be used for
+# the MathJax output. For more details about the output format see MathJax
+# version 2 (see:
+# http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3
+# (see:
+# http://docs.mathjax.org/en/latest/web/components/output.html).
+# Possible values are: HTML-CSS (which is slower, but has the best
+# compatibility. This is the name for Mathjax version 2, for MathJax version 3
+# this will be translated into chtml), NativeMML (i.e. MathML. Only supported
+# for NathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This
+# is the name for Mathjax version 3, for MathJax version 2 this will be
+# translated into HTML-CSS) and SVG.
+# The default value is: HTML-CSS.
+# This tag requires that the tag USE_MATHJAX is set to YES.
+
+MATHJAX_FORMAT         = HTML-CSS
+
+# When MathJax is enabled you need to specify the location relative to the HTML
+# output directory using the MATHJAX_RELPATH option. The destination directory
+# should contain the MathJax.js script. For instance, if the mathjax directory
+# is located at the same level as the HTML output directory, then
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
+# Content Delivery Network so you can quickly see the result without installing
+# MathJax. However, it is strongly recommended to install a local copy of
+# MathJax from https://www.mathjax.org before deployment. The default value is:
+# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2
+# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3
+# This tag requires that the tag USE_MATHJAX is set to YES.
+
+MATHJAX_RELPATH        =
+
+# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
+# extension names that should be enabled during MathJax rendering. For example
+# for MathJax version 2 (see
+# https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions):
+# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
+# For example for MathJax version 3 (see
+# http://docs.mathjax.org/en/latest/input/tex/extensions/index.html):
+# MATHJAX_EXTENSIONS = ams
+# This tag requires that the tag USE_MATHJAX is set to YES.
+
+MATHJAX_EXTENSIONS     =
+
+# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
+# of code that will be used on startup of the MathJax code. See the MathJax site
+# (see:
+# http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an
+# example see the documentation.
+# This tag requires that the tag USE_MATHJAX is set to YES.
+
+MATHJAX_CODEFILE       =
+
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box for
+# the HTML output. The underlying search engine uses javascript and DHTML and
+# should work on any modern browser. Note that when using HTML help
+# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
+# there is already a search function so this one should typically be disabled.
+# For large projects the javascript based search engine can be slow, then
+# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
+# search using the keyboard; to jump to the search box use <access key> + S
+# (what the <access key> is depends on the OS and browser, but it is typically
+# <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
+# key> to jump into the search results window, the results can be navigated
+# using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
+# the search. The filter options can be selected when the cursor is inside the
+# search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
+# to select a filter and <Enter> or <escape> to activate or cancel the filter
+# option.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+SEARCHENGINE           = YES
+
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
+# implemented using a web server instead of a web client using JavaScript. There
+# are two flavors of web server based searching depending on the EXTERNAL_SEARCH
+# setting. When disabled, doxygen will generate a PHP script for searching and
+# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
+# and searching needs to be provided by external tools. See the section
+# "External Indexing and Searching" for details.
+# The default value is: NO.
+# This tag requires that the tag SEARCHENGINE is set to YES.
+
+SERVER_BASED_SEARCH    = NO
+
+# When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
+# script for searching. Instead the search results are written to an XML file
+# which needs to be processed by an external indexer. Doxygen will invoke an
+# external search engine pointed to by the SEARCHENGINE_URL option to obtain the
+# search results.
+#
+# Doxygen ships with an example indexer (doxyindexer) and search engine
+# (doxysearch.cgi) which are based on the open source search engine library
+# Xapian (see:
+# https://xapian.org/).
+#
+# See the section "External Indexing and Searching" for details.
+# The default value is: NO.
+# This tag requires that the tag SEARCHENGINE is set to YES.
+
+EXTERNAL_SEARCH        = NO
+
+# The SEARCHENGINE_URL should point to a search engine hosted by a web server
+# which will return the search results when EXTERNAL_SEARCH is enabled.
+#
+# Doxygen ships with an example indexer (doxyindexer) and search engine
+# (doxysearch.cgi) which are based on the open source search engine library
+# Xapian (see:
+# https://xapian.org/). See the section "External Indexing and Searching" for
+# details.
+# This tag requires that the tag SEARCHENGINE is set to YES.
+
+SEARCHENGINE_URL       =
+
+# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
+# search data is written to a file for indexing by an external tool. With the
+# SEARCHDATA_FILE tag the name of this file can be specified.
+# The default file is: searchdata.xml.
+# This tag requires that the tag SEARCHENGINE is set to YES.
+
+SEARCHDATA_FILE        = searchdata.xml
+
+# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
+# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
+# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
+# projects and redirect the results back to the right project.
+# This tag requires that the tag SEARCHENGINE is set to YES.
+
+EXTERNAL_SEARCH_ID     =
+
+# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
+# projects other than the one defined by this configuration file, but that are
+# all added to the same external search index. Each project needs to have a
+# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
+# to a relative location where the documentation can be found. The format is:
+# EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
+# This tag requires that the tag SEARCHENGINE is set to YES.
+
+EXTRA_SEARCH_MAPPINGS  =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the LaTeX output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
+# The default value is: YES.
+
+GENERATE_LATEX         = YES
+
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
+# it.
+# The default directory is: latex.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_OUTPUT           = latex
+
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
+# invoked.
+#
+# Note that when not enabling USE_PDFLATEX the default is latex when enabling
+# USE_PDFLATEX the default is pdflatex and when in the later case latex is
+# chosen this is overwritten by pdflatex. For specific output languages the
+# default can have been set differently, this depends on the implementation of
+# the output language.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_CMD_NAME         =
+
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
+# index for LaTeX.
+# Note: This tag is used in the Makefile / make.bat.
+# See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
+# (.tex).
+# The default file is: makeindex.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+MAKEINDEX_CMD_NAME     = makeindex
+
+# The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
+# generate index for LaTeX. In case there is no backslash (\) as first character
+# it will be automatically added in the LaTeX code.
+# Note: This tag is used in the generated output file (.tex).
+# See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
+# The default value is: makeindex.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_MAKEINDEX_CMD    = makeindex
+
+# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
+# documents. This may be useful for small projects and may help to save some
+# trees in general.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+COMPACT_LATEX          = NO
+
+# The PAPER_TYPE tag can be used to set the paper type that is used by the
+# printer.
+# Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
+# 14 inches) and executive (7.25 x 10.5 inches).
+# The default value is: a4.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+PAPER_TYPE             = a4
+
+# The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
+# that should be included in the LaTeX output. The package can be specified just
+# by its name or with the correct syntax as to be used with the LaTeX
+# \usepackage command. To get the times font for instance you can specify :
+# EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
+# To use the option intlimits with the amsmath package you can specify:
+# EXTRA_PACKAGES=[intlimits]{amsmath}
+# If left blank no extra packages will be included.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+EXTRA_PACKAGES         =
+
+# The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for
+# the generated LaTeX document. The header should contain everything until the
+# first chapter. If it is left blank doxygen will generate a standard header. It
+# is highly recommended to start with a default header using
+# doxygen -w latex new_header.tex new_footer.tex new_stylesheet.sty
+# and then modify the file new_header.tex. See also section "Doxygen usage" for
+# information on how to generate the default header that doxygen normally uses.
+#
+# Note: Only use a user-defined header if you know what you are doing!
+# Note: The header is subject to change so you typically have to regenerate the
+# default header when upgrading to a newer version of doxygen. The following
+# commands have a special meaning inside the header (and footer): For a
+# description of the possible markers and block names see the documentation.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_HEADER           =
+
+# The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for
+# the generated LaTeX document. The footer should contain everything after the
+# last chapter. If it is left blank doxygen will generate a standard footer. See
+# LATEX_HEADER for more information on how to generate a default footer and what
+# special commands can be used inside the footer. See also section "Doxygen
+# usage" for information on how to generate the default footer that doxygen
+# normally uses. Note: Only use a user-defined footer if you know what you are
+# doing!
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_FOOTER           =
+
+# The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
+# LaTeX style sheets that are included after the standard style sheets created
+# by doxygen. Using this option one can overrule certain style aspects. Doxygen
+# will copy the style sheet files to the output directory.
+# Note: The order of the extra style sheet files is of importance (e.g. the last
+# style sheet in the list overrules the setting of the previous ones in the
+# list).
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_EXTRA_STYLESHEET =
+
+# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
+# other source files which should be copied to the LATEX_OUTPUT output
+# directory. Note that the files will be copied as-is; there are no commands or
+# markers available.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_EXTRA_FILES      =
+
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
+# prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
+# contain links (just like the HTML output) instead of page references. This
+# makes the output suitable for online browsing using a PDF viewer.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+PDF_HYPERLINKS         = YES
+
+# If the USE_PDFLATEX tag is set to YES, doxygen will use the engine as
+# specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX
+# files. Set this option to YES, to get a higher quality PDF documentation.
+#
+# See also section LATEX_CMD_NAME for selecting the engine.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+USE_PDFLATEX           = YES
+
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
+# command to the generated LaTeX files. This will instruct LaTeX to keep running
+# if errors occur, instead of asking the user for help.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_BATCHMODE        = NO
+
+# If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
+# index chapters (such as File Index, Compound Index, etc.) in the output.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_HIDE_INDICES     = NO
+
+# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
+# bibliography, e.g. plainnat, or ieeetr. See
+# https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
+# The default value is: plain.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_BIB_STYLE        = plain
+
+# If the LATEX_TIMESTAMP tag is set to YES then the footer of each generated
+# page will contain the date and time when the page was generated. Setting this
+# to NO can help when comparing the output of multiple runs.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_TIMESTAMP        = NO
+
+# The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
+# path from which the emoji images will be read. If a relative path is entered,
+# it will be relative to the LATEX_OUTPUT directory. If left blank the
+# LATEX_OUTPUT directory will be used.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_EMOJI_DIRECTORY  =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the RTF output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
+# RTF output is optimized for Word 97 and may not look too pretty with other RTF
+# readers/editors.
+# The default value is: NO.
+
+GENERATE_RTF           = NO
+
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
+# it.
+# The default directory is: rtf.
+# This tag requires that the tag GENERATE_RTF is set to YES.
+
+RTF_OUTPUT             = rtf
+
+# If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
+# documents. This may be useful for small projects and may help to save some
+# trees in general.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_RTF is set to YES.
+
+COMPACT_RTF            = NO
+
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
+# contain hyperlink fields. The RTF file will contain links (just like the HTML
+# output) instead of page references. This makes the output suitable for online
+# browsing using Word or some other Word compatible readers that support those
+# fields.
+#
+# Note: WordPad (write) and others do not support links.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_RTF is set to YES.
+
+RTF_HYPERLINKS         = NO
+
+# Load stylesheet definitions from file. Syntax is similar to doxygen's
+# configuration file, i.e. a series of assignments. You only have to provide
+# replacements, missing definitions are set to their default value.
+#
+# See also section "Doxygen usage" for information on how to generate the
+# default style sheet that doxygen normally uses.
+# This tag requires that the tag GENERATE_RTF is set to YES.
+
+RTF_STYLESHEET_FILE    =
+
+# Set optional variables used in the generation of an RTF document. Syntax is
+# similar to doxygen's configuration file. A template extensions file can be
+# generated using doxygen -e rtf extensionFile.
+# This tag requires that the tag GENERATE_RTF is set to YES.
+
+RTF_EXTENSIONS_FILE    =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the man page output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
+# classes and files.
+# The default value is: NO.
+
+GENERATE_MAN           = NO
+
+# The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
+# it. A directory man3 will be created inside the directory specified by
+# MAN_OUTPUT.
+# The default directory is: man.
+# This tag requires that the tag GENERATE_MAN is set to YES.
+
+MAN_OUTPUT             = man
+
+# The MAN_EXTENSION tag determines the extension that is added to the generated
+# man pages. In case the manual section does not start with a number, the number
+# 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
+# optional.
+# The default value is: .3.
+# This tag requires that the tag GENERATE_MAN is set to YES.
+
+MAN_EXTENSION          = .3
+
+# The MAN_SUBDIR tag determines the name of the directory created within
+# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
+# MAN_EXTENSION with the initial . removed.
+# This tag requires that the tag GENERATE_MAN is set to YES.
+
+MAN_SUBDIR             =
+
+# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
+# will generate one additional man file for each entity documented in the real
+# man page(s). These additional files only source the real man page, but without
+# them the man command would be unable to find the correct page.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_MAN is set to YES.
+
+MAN_LINKS              = NO
+
+#---------------------------------------------------------------------------
+# Configuration options related to the XML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
+# captures the structure of the code including all documentation.
+# The default value is: NO.
+
+GENERATE_XML           = NO
+
+# The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
+# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
+# it.
+# The default directory is: xml.
+# This tag requires that the tag GENERATE_XML is set to YES.
+
+XML_OUTPUT             = xml
+
+# If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
+# listings (including syntax highlighting and cross-referencing information) to
+# the XML output. Note that enabling this will significantly increase the size
+# of the XML output.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_XML is set to YES.
+
+XML_PROGRAMLISTING     = YES
+
+# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include
+# namespace members in file scope as well, matching the HTML output.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_XML is set to YES.
+
+XML_NS_MEMB_FILE_SCOPE = NO
+
+#---------------------------------------------------------------------------
+# Configuration options related to the DOCBOOK output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
+# that can be used to generate PDF.
+# The default value is: NO.
+
+GENERATE_DOCBOOK       = NO
+
+# The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
+# front of it.
+# The default directory is: docbook.
+# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
+
+DOCBOOK_OUTPUT         = docbook
+
+#---------------------------------------------------------------------------
+# Configuration options for the AutoGen Definitions output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
+# AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures
+# the structure of the code including all documentation. Note that this feature
+# is still experimental and incomplete at the moment.
+# The default value is: NO.
+
+GENERATE_AUTOGEN_DEF   = NO
+
+#---------------------------------------------------------------------------
+# Configuration options related to Sqlite3 output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_SQLITE3 tag is set to YES doxygen will generate a Sqlite3
+# database with symbols found by doxygen stored in tables.
+# Note: The availability of this option depends on whether or not doxygen was
+# generated with the -Duse_sqlite3=ON option for CMake.
+# The default value is: NO.
+
+GENERATE_SQLITE3       = NO
+
+# The SQLITE3_OUTPUT tag is used to specify where the Sqlite3 database will be
+# put. If a relative path is entered the value of OUTPUT_DIRECTORY will be put
+# in front of it.
+# Note: The availability of this option depends on whether or not doxygen was
+# generated with the -Duse_sqlite3=ON option for CMake.
+# The default directory is: sqlite3.
+# This tag requires that the tag GENERATE_SQLITE3 is set to YES.
+
+SQLITE3_OUTPUT         = sqlite3
+
+# The SQLITE3_OVERWRITE_DB tag is set to YES, the existing doxygen_sqlite3.db
+# database file will be recreated with each doxygen run. If set to NO, doxygen
+# will warn if an a database file is already found and not modify it.
+# Note: The availability of this option depends on whether or not doxygen was
+# generated with the -Duse_sqlite3=ON option for CMake.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_SQLITE3 is set to YES.
+
+SQLITE3_RECREATE_DB    = YES
+
+#---------------------------------------------------------------------------
+# Configuration options related to the Perl module output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
+# file that captures the structure of the code including all documentation.
+#
+# Note that this feature is still experimental and incomplete at the moment.
+# The default value is: NO.
+
+GENERATE_PERLMOD       = NO
+
+# If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
+# Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
+# output from the Perl module output.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_PERLMOD is set to YES.
+
+PERLMOD_LATEX          = NO
+
+# If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
+# formatted so it can be parsed by a human reader. This is useful if you want to
+# understand what is going on. On the other hand, if this tag is set to NO, the
+# size of the Perl module output will be much smaller and Perl will parse it
+# just the same.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_PERLMOD is set to YES.
+
+PERLMOD_PRETTY         = YES
+
+# The names of the make variables in the generated doxyrules.make file are
+# prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
+# so different doxyrules.make files included by the same Makefile don't
+# overwrite each other's variables.
+# This tag requires that the tag GENERATE_PERLMOD is set to YES.
+
+PERLMOD_MAKEVAR_PREFIX =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the preprocessor
+#---------------------------------------------------------------------------
+
+# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
+# C-preprocessor directives found in the sources and include files.
+# The default value is: YES.
+
+ENABLE_PREPROCESSING   = YES
+
+# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
+# in the source code. If set to NO, only conditional compilation will be
+# performed. Macro expansion can be done in a controlled way by setting
+# EXPAND_ONLY_PREDEF to YES.
+# The default value is: NO.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+
+MACRO_EXPANSION        = NO
+
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
+# the macro expansion is limited to the macros specified with the PREDEFINED and
+# EXPAND_AS_DEFINED tags.
+# The default value is: NO.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+
+EXPAND_ONLY_PREDEF     = NO
+
+# If the SEARCH_INCLUDES tag is set to YES, the include files in the
+# INCLUDE_PATH will be searched if a #include is found.
+# The default value is: YES.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+
+SEARCH_INCLUDES        = YES
+
+# The INCLUDE_PATH tag can be used to specify one or more directories that
+# contain include files that are not input files but should be processed by the
+# preprocessor.
+# This tag requires that the tag SEARCH_INCLUDES is set to YES.
+
+INCLUDE_PATH           =
+
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
+# patterns (like *.h and *.hpp) to filter out the header-files in the
+# directories. If left blank, the patterns specified with FILE_PATTERNS will be
+# used.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+
+INCLUDE_FILE_PATTERNS  =
+
+# The PREDEFINED tag can be used to specify one or more macro names that are
+# defined before the preprocessor is started (similar to the -D option of e.g.
+# gcc). The argument of the tag is a list of macros of the form: name or
+# name=definition (no spaces). If the definition and the "=" are omitted, "=1"
+# is assumed. To prevent a macro definition from being undefined via #undef or
+# recursively expanded use the := operator instead of the = operator.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+
+PREDEFINED             =
+
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
+# tag can be used to specify a list of macro names that should be expanded. The
+# macro definition that is found in the sources will be used. Use the PREDEFINED
+# tag if you want to use a different macro definition that overrules the
+# definition found in the source code.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+
+EXPAND_AS_DEFINED      =
+
+# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
+# remove all references to function-like macros that are alone on a line, have
+# an all uppercase name, and do not end with a semicolon. Such function macros
+# are typically used for boiler-plate code, and will confuse the parser if not
+# removed.
+# The default value is: YES.
+# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
+
+SKIP_FUNCTION_MACROS   = YES
+
+#---------------------------------------------------------------------------
+# Configuration options related to external references
+#---------------------------------------------------------------------------
+
+# The TAGFILES tag can be used to specify one or more tag files. For each tag
+# file the location of the external documentation should be added. The format of
+# a tag file without this location is as follows:
+# TAGFILES = file1 file2 ...
+# Adding location for the tag files is done as follows:
+# TAGFILES = file1=loc1 "file2 = loc2" ...
+# where loc1 and loc2 can be relative or absolute paths or URLs. See the
+# section "Linking to external documentation" for more information about the use
+# of tag files.
+# Note: Each tag file must have a unique name (where the name does NOT include
+# the path). If a tag file is not located in the directory in which doxygen is
+# run, you must also specify the path to the tagfile here.
+
+TAGFILES               =
+
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create a
+# tag file that is based on the input files it reads. See section "Linking to
+# external documentation" for more information about the usage of tag files.
+
+GENERATE_TAGFILE       =
+
+# If the ALLEXTERNALS tag is set to YES, all external class will be listed in
+# the class index. If set to NO, only the inherited external classes will be
+# listed.
+# The default value is: NO.
+
+ALLEXTERNALS           = NO
+
+# If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
+# in the modules index. If set to NO, only the current project's groups will be
+# listed.
+# The default value is: YES.
+
+EXTERNAL_GROUPS        = YES
+
+# If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
+# the related pages index. If set to NO, only the current project's pages will
+# be listed.
+# The default value is: YES.
+
+EXTERNAL_PAGES         = YES
+
+#---------------------------------------------------------------------------
+# Configuration options related to the dot tool
+#---------------------------------------------------------------------------
+
+# You can include diagrams made with dia in doxygen documentation. Doxygen will
+# then run dia to produce the diagram and insert it in the documentation. The
+# DIA_PATH tag allows you to specify the directory where the dia binary resides.
+# If left empty dia is assumed to be found in the default search path.
+
+DIA_PATH               =
+
+# If set to YES the inheritance and collaboration graphs will hide inheritance
+# and usage relations if the target is undocumented or is not a class.
+# The default value is: YES.
+
+HIDE_UNDOC_RELATIONS   = YES
+
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
+# available from the path. This tool is part of Graphviz (see:
+# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
+# Bell Labs. The other options in this section have no effect if this option is
+# set to NO
+# The default value is: NO.
+
+HAVE_DOT               = NO
+
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
+# to run in parallel. When set to 0 doxygen will base this on the number of
+# processors available in the system. You can set it explicitly to a value
+# larger than 0 to get control over the balance between CPU load and processing
+# speed.
+# Minimum value: 0, maximum value: 32, default value: 0.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_NUM_THREADS        = 0
+
+# When you want a differently looking font in the dot files that doxygen
+# generates you can specify the font name using DOT_FONTNAME. You need to make
+# sure dot is able to find the font, which can be done by putting it in a
+# standard location or by setting the DOTFONTPATH environment variable or by
+# setting DOT_FONTPATH to the directory containing the font.
+# The default value is: Helvetica.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_FONTNAME           = Helvetica
+
+# The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
+# dot graphs.
+# Minimum value: 4, maximum value: 24, default value: 10.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_FONTSIZE           = 10
+
+# By default doxygen will tell dot to use the default font as specified with
+# DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
+# the path where dot can find it using this tag.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_FONTPATH           =
+
+# If the CLASS_GRAPH tag is set to YES (or GRAPH) then doxygen will generate a
+# graph for each documented class showing the direct and indirect inheritance
+# relations. In case HAVE_DOT is set as well dot will be used to draw the graph,
+# otherwise the built-in generator will be used. If the CLASS_GRAPH tag is set
+# to TEXT the direct and indirect inheritance relations will be shown as texts /
+# links.
+# Possible values are: NO, YES, TEXT and GRAPH.
+# The default value is: YES.
+
+CLASS_GRAPH            = YES
+
+# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
+# graph for each documented class showing the direct and indirect implementation
+# dependencies (inheritance, containment, and class references variables) of the
+# class with other documented classes.
+# The default value is: YES.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+COLLABORATION_GRAPH    = YES
+
+# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
+# groups, showing the direct groups dependencies.
+# The default value is: YES.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+GROUP_GRAPHS           = YES
+
+# If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
+# collaboration diagrams in a style similar to the OMG's Unified Modeling
+# Language.
+# The default value is: NO.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+UML_LOOK               = NO
+
+# If the UML_LOOK tag is enabled, the fields and methods are shown inside the
+# class node. If there are many fields or methods and many nodes the graph may
+# become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
+# number of items for each type to make the size more manageable. Set this to 0
+# for no limit. Note that the threshold may be exceeded by 50% before the limit
+# is enforced. So when you set the threshold to 10, up to 15 fields may appear,
+# but if the number exceeds 15, the total amount of fields shown is limited to
+# 10.
+# Minimum value: 0, maximum value: 100, default value: 10.
+# This tag requires that the tag UML_LOOK is set to YES.
+
+UML_LIMIT_NUM_FIELDS   = 10
+
+# If the DOT_UML_DETAILS tag is set to NO, doxygen will show attributes and
+# methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS
+# tag is set to YES, doxygen will add type and arguments for attributes and
+# methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, doxygen
+# will not generate fields with class member information in the UML graphs. The
+# class diagrams will look similar to the default class diagrams but using UML
+# notation for the relationships.
+# Possible values are: NO, YES and NONE.
+# The default value is: NO.
+# This tag requires that the tag UML_LOOK is set to YES.
+
+DOT_UML_DETAILS        = NO
+
+# The DOT_WRAP_THRESHOLD tag can be used to set the maximum number of characters
+# to display on a single line. If the actual line length exceeds this threshold
+# significantly it will wrapped across multiple lines. Some heuristics are apply
+# to avoid ugly line breaks.
+# Minimum value: 0, maximum value: 1000, default value: 17.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_WRAP_THRESHOLD     = 17
+
+# If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
+# collaboration graphs will show the relations between templates and their
+# instances.
+# The default value is: NO.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+TEMPLATE_RELATIONS     = NO
+
+# If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
+# YES then doxygen will generate a graph for each documented file showing the
+# direct and indirect include dependencies of the file with other documented
+# files.
+# The default value is: YES.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+INCLUDE_GRAPH          = YES
+
+# If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
+# set to YES then doxygen will generate a graph for each documented file showing
+# the direct and indirect include dependencies of the file with other documented
+# files.
+# The default value is: YES.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+INCLUDED_BY_GRAPH      = YES
+
+# If the CALL_GRAPH tag is set to YES then doxygen will generate a call
+# dependency graph for every global function or class method.
+#
+# Note that enabling this option will significantly increase the time of a run.
+# So in most cases it will be better to enable call graphs for selected
+# functions only using the \callgraph command. Disabling a call graph can be
+# accomplished by means of the command \hidecallgraph.
+# The default value is: NO.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+CALL_GRAPH             = NO
+
+# If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
+# dependency graph for every global function or class method.
+#
+# Note that enabling this option will significantly increase the time of a run.
+# So in most cases it will be better to enable caller graphs for selected
+# functions only using the \callergraph command. Disabling a caller graph can be
+# accomplished by means of the command \hidecallergraph.
+# The default value is: NO.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+CALLER_GRAPH           = NO
+
+# If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
+# hierarchy of all classes instead of a textual one.
+# The default value is: YES.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+GRAPHICAL_HIERARCHY    = YES
+
+# If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
+# dependencies a directory has on other directories in a graphical way. The
+# dependency relations are determined by the #include relations between the
+# files in the directories.
+# The default value is: YES.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DIRECTORY_GRAPH        = YES
+
+# The DIR_GRAPH_MAX_DEPTH tag can be used to limit the maximum number of levels
+# of child directories generated in directory dependency graphs by dot.
+# Minimum value: 1, maximum value: 25, default value: 1.
+# This tag requires that the tag DIRECTORY_GRAPH is set to YES.
+
+DIR_GRAPH_MAX_DEPTH    = 1
+
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
+# generated by dot. For an explanation of the image formats see the section
+# output formats in the documentation of the dot tool (Graphviz (see:
+# http://www.graphviz.org/)).
+# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
+# to make the SVG files visible in IE 9+ (other browsers do not have this
+# requirement).
+# Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,
+# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
+# png:gdiplus:gdiplus.
+# The default value is: png.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_IMAGE_FORMAT       = png
+
+# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
+# enable generation of interactive SVG images that allow zooming and panning.
+#
+# Note that this requires a modern browser other than Internet Explorer. Tested
+# and working are Firefox, Chrome, Safari, and Opera.
+# Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
+# the SVG files visible. Older versions of IE do not have SVG support.
+# The default value is: NO.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+INTERACTIVE_SVG        = NO
+
+# The DOT_PATH tag can be used to specify the path where the dot tool can be
+# found. If left blank, it is assumed the dot tool can be found in the path.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_PATH               =
+
+# The DOTFILE_DIRS tag can be used to specify one or more directories that
+# contain dot files that are included in the documentation (see the \dotfile
+# command).
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOTFILE_DIRS           =
+
+# The MSCFILE_DIRS tag can be used to specify one or more directories that
+# contain msc files that are included in the documentation (see the \mscfile
+# command).
+
+MSCFILE_DIRS           =
+
+# The DIAFILE_DIRS tag can be used to specify one or more directories that
+# contain dia files that are included in the documentation (see the \diafile
+# command).
+
+DIAFILE_DIRS           =
+
+# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
+# path where java can find the plantuml.jar file or to the filename of jar file
+# to be used. If left blank, it is assumed PlantUML is not used or called during
+# a preprocessing step. Doxygen will generate a warning when it encounters a
+# \startuml command in this case and will not generate output for the diagram.
+
+PLANTUML_JAR_PATH      =
+
+# When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
+# configuration file for plantuml.
+
+PLANTUML_CFG_FILE      =
+
+# When using plantuml, the specified paths are searched for files specified by
+# the !include statement in a plantuml block.
+
+PLANTUML_INCLUDE_PATH  =
+
+# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
+# that will be shown in the graph. If the number of nodes in a graph becomes
+# larger than this value, doxygen will truncate the graph, which is visualized
+# by representing a node as a red box. Note that doxygen if the number of direct
+# children of the root node in a graph is already larger than
+# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
+# the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
+# Minimum value: 0, maximum value: 10000, default value: 50.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_GRAPH_MAX_NODES    = 50
+
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
+# generated by dot. A depth value of 3 means that only nodes reachable from the
+# root by following a path via at most 3 edges will be shown. Nodes that lay
+# further from the root node will be omitted. Note that setting this option to 1
+# or 2 may greatly reduce the computation time needed for large code bases. Also
+# note that the size of a graph can be further restricted by
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
+# Minimum value: 0, maximum value: 1000, default value: 0.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+MAX_DOT_GRAPH_DEPTH    = 0
+
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
+# background. This is disabled by default, because dot on Windows does not seem
+# to support this out of the box.
+#
+# Warning: Depending on the platform used, enabling this option may lead to
+# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
+# read).
+# The default value is: NO.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_TRANSPARENT        = NO
+
+# Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
+# files in one run (i.e. multiple -o and -T options on the command line). This
+# makes dot run faster, but since only newer versions of dot (>1.8.10) support
+# this, this feature is disabled by default.
+# The default value is: NO.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_MULTI_TARGETS      = NO
+
+# If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
+# explaining the meaning of the various boxes and arrows in the dot generated
+# graphs.
+# Note: This tag requires that UML_LOOK isn't set, i.e. the doxygen internal
+# graphical representation for inheritance and collaboration diagrams is used.
+# The default value is: YES.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+GENERATE_LEGEND        = YES
+
+# If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate
+# files that are used to generate the various graphs.
+#
+# Note: This setting is not only used for dot files but also for msc temporary
+# files.
+# The default value is: YES.
+
+DOT_CLEANUP            = YES
diff --git a/docs/src/development.dox b/docs/src/development.dox
new file mode 100644
index 0000000..bcae8c2
--- /dev/null
+++ b/docs/src/development.dox
@@ -0,0 +1,65 @@
+/**
+
+\page development Development
+
+Overview
+--------
+We use:
+- Catch2 library for writing tests.
+  \warning We are currently on version 2.
+- Doxygen to generate documentation.
+- clangd for hints.
+- clang-format for code formatting.
+- GNU Make to build the project.
+  You can see the targets, flags and arguments by runnig `make help`.
+
+
+Code style
+----------
+We are using a WebKit-based coding style with some differences,
+see `.clang-format` at the project root.
+
+Please use the _clang-format_ to keep code style.
+
+Also you can automatically run formatting with `make format`.
+
+
+Licensing rules
+---------------
+Add an SPDX license notice to top of every file you create.
+Notice format:
+```
+/* SPDX-License-Identifier: <SPDX License Expression> */
+```
+
+If you edit exist file, add your copyright info.
+Copyright notice format:
+```
+/* Copyright <YEAR> <AUTHOR> */
+```
+
+
+Writing tests
+-------------
+For writing tests we are using the
+[Catch2](https://github.com/catchorg/Catch2) library.
+Read it's
+[tutorial](https://github.com/catchorg/Catch2/blob/devel/docs/tutorial.md#top)
+to be aware.
+
+Tests placed at the `tests` directory of the project root and can be built
+by ranning `make run_tests`. `run_tests` executable will be built.
+
+
+Writing docs
+------------
+All code of this project should be documented,
+for docs generation we are use [Doxygen](http://doxygen.nl).
+
+See Doxygen documentation and existing code to see an examples.
+
+Rules:
+- Documentation pages like this placed in `docs/src`.
+- Use Qt-style documentation.
+
+ */
diff --git a/docs/src/get_started.dox b/docs/src/get_started.dox
new file mode 100644
index 0000000..1986fcb
--- /dev/null
+++ b/docs/src/get_started.dox
@@ -0,0 +1,40 @@
+/**
+
+\page get_started Get Started
+
+Installation
+------------
+Run the following commands:
+```sh
+git clone http://git.vilor.one/rapida/rapida && cd rapida
+make install
+```
+
+This will create the shared and static libraries
+and install them on your system.
+
+C example:
+----------
+\include minimal.c
+
+C++ example:
+------------
+
+\include minimal.cxx
+
+More examples you can find at http://git.vilor.one/rapida/rapida/examples
+
+Building
+--------
+If you have installed Rapida on your system, just link it to your program.
+
+- **rapida** for C apps.
+- **rapidaxx** for C++.
+
+For example:
+```sh
+gcc myapp.c -lrapida     # link C library
+g++ myapp.cxx -lrapidaxx # link C++ library
+```
+
+*/
diff --git a/docs/src/index.dox b/docs/src/index.dox
new file mode 100644
index 0000000..53fffec
--- /dev/null
+++ b/docs/src/index.dox
@@ -0,0 +1,11 @@
+/**
+
+\mainpage Rapida Manual
+
+Rapida is the fast web framework written in C and C++.
+
+Table of contents:
+1. \subpage get_started
+2. \subpage development
+
+*/
diff --git a/examples/Makefile b/examples/Makefile
new file mode 100644
index 0000000..77a858e
--- /dev/null
+++ b/examples/Makefile
@@ -0,0 +1,22 @@
+include ../config.mk
+
+CXXSRC := $(shell find cxx -type f -name '*.cxx')
+CXXBINS := $(CXXSRC:.cxx=)
+CSRC := $(shell find c -type f -name '*.c')
+CBINS := $(CSRC:.c=)
+
+all: $(CBINS) $(CXXBINS)
+
+%: %.c ../librapida.a
+	$(CC) $(CFLAGS) -I../include $^ -o $@ $(LDFLAGS)
+
+%: %.cxx ../librapidaxx.a
+	$(CXX) $(CXXFLAGS) -std=c++11 -I../include $^ -o $@ $(LDFLAGS)
+
+../librapida.a:
+	cd .. && make librapida.a
+
+../librapidaxx.a:
+	cd .. && make librapidaxx.a
+
+.PHONY: ../librapida.a ../librapidaxx.a
diff --git a/examples/README.md b/examples/README.md
new file mode 100644
index 0000000..097a157
--- /dev/null
+++ b/examples/README.md
@@ -0,0 +1,20 @@
+Examples
+========
+This example shows how to use a simple _rpd_ application with NGINX.
+
+NGINX configuration
+-------------------
+In the location you want to process with rpd, provide the following lines:
+
+```nginx
+fastcgi_pass unix: /tmp/rpd.example.sock;
+include fastcgi_params;
+```
+
+Where `/tmp/rpd.example.sock` is the UNIX socket you passed
+to the rpd_app instance and fastcgi_params is the list
+of variables that NGINX passes through the FastCGI protocol.
+
+See examples:
+* [example-site.nginx.conf](example-site.nginx.conf)
+* [fastcgi_params](fastcgi_params)
diff --git a/examples/c/example.c b/examples/c/example.c
new file mode 100644
index 0000000..a5d9e3a
--- /dev/null
+++ b/examples/c/example.c
@@ -0,0 +1,56 @@
+#include "../../include/rapida.h"
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+
+static void products_handler(rpd_req *req, rpd_res *res, void *userdata)
+{
+    char *body = "<!DOCTYPE html>"
+                 "<html>"
+                 "<head><title>Product</title></head>"
+                 "<body>"
+                 "<h1>Product page</h1>"
+                 "<pre>"
+                 "Category: %s\n"
+                 "Id: %s"
+                 "</pre>"
+                 "</body>"
+                 "</html>";
+    rpd_keyval_item *cat = rpd_keyval_find(&req->params, "category");
+    rpd_keyval_item *id = rpd_keyval_find(&req->params, "id");
+
+    if (!cat || !id) {
+        res->status = rpd_res_st_internal_server_error;
+        return;
+    }
+
+    int bufflen = strlen(body) + strlen(cat->val) + strlen(id->val);
+    res->body = (char *) malloc(sizeof(char) * (bufflen + 1));
+    if (!res->body) {
+        res->status = rpd_res_st_internal_server_error;
+        return;
+    }
+    res->body[bufflen] = '\0';
+
+    sprintf(res->body, body, cat->val, id->val);
+
+    res->status = rpd_res_st_ok;
+
+    /*
+     * place all values in heap, please,
+     * because after call handler
+     * `req` and `res` will be freed
+     */
+    res->content_type = strdup("text/html");
+}
+
+int main()
+{
+    rpd_app app;
+    rpd_app_create(&app, "/tmp/rapida.example.socket");
+
+    rpd_app_add_route(&app, "/products/:category/:id", &products_handler, NULL);
+
+    rpd_app_start(&app);
+    return 0;
+}
diff --git a/examples/c/minimal.c b/examples/c/minimal.c
new file mode 100644
index 0000000..7db18d8
--- /dev/null
+++ b/examples/c/minimal.c
@@ -0,0 +1,54 @@
+#include "../../include/rapida.h"
+#include <string.h> /* for strdup() */
+#include <stdio.h>
+
+
+/*
+ * \brief Process home page request.
+ *
+ * \param req Request.
+ * \param res Response.
+ * \param userdata Additional data that you can pass to this handler
+ *                 when adding a route.
+ */
+static void home_page_handler(rpd_req *req, rpd_res *res, void *userdata)
+{
+    /* Check request method */
+    switch (req->method) {
+    case GET:
+        /* Process GET request */
+        res->status = rpd_res_st_ok;
+
+        /* Please allocate data on the heap,
+         * because after calling this handler
+         * Rapida will free it all.
+         */
+        res->content_type = strdup("text/plain");
+        res->body = strdup("Hello World!");
+        break;
+    default:
+        /* Other request methods are not implemented,
+         * so set the appropriate response status.
+         */
+        res->status = rpd_res_st_not_implemented;
+        break;
+    }
+
+    /*
+     * You don't have to do something like send a response.
+     * Rapida will do this after calling this handler.
+     */
+}
+
+int main()
+{
+    rpd_app app;
+    /* Initialize application. */
+    rpd_app_create(&app, "/tmp/webapp.socket");
+
+    /* Add home "/" page handler. */
+    rpd_app_add_route(&app, "/", &home_page_handler, NULL);
+
+    /* Run the application and return its status code. */
+    return rpd_app_start(&app);
+}
diff --git a/examples/cxx/example.cxx b/examples/cxx/example.cxx
new file mode 100644
index 0000000..dd2d42a
--- /dev/null
+++ b/examples/cxx/example.cxx
@@ -0,0 +1,52 @@
+#include "../../include/rapida.hxx"
+#include <sstream>
+
+class ProductRoute : public rpd::Route {
+protected:
+    virtual void handle_get(const rpd::Request &req, rpd::Response &res) override
+    {
+        rpd::KeyVal params = req.params();
+        const char *cat = params["category"];
+        const char *id = params["id"];
+
+        std::string body = "<!DOCTYPE html>"
+                           "<html>"
+                           "<head><title>Product</title></head>"
+                           "<body>"
+                           "<h1>Product page</h1>"
+                           "<pre>";
+
+        body += "Category: ";
+        body += cat;
+        body += "\n";
+
+        body += "Id: ";
+        body += id;
+
+        body += "</pre>"
+                "</body>"
+                "</html>\r\n";
+
+        handle_head(req, res);
+        res.body(body.c_str());
+    }
+
+    virtual void handle_head(const rpd::Request &req, rpd::Response &res) override
+    {
+        res.status(rpd_res_st_ok);
+        res.content_type("text/html");
+    }
+};
+
+int main()
+{
+    rpd::App app("/tmp/rapida.example.socket");
+
+    /*
+     * `category` and `id` are dynamic parameters
+     * that can be found in the `params` field in `Route`.
+     */
+    app.add_route("/products/:category/:id", new ProductRoute());
+
+    return app.start();
+}
diff --git a/examples/cxx/minimal.cxx b/examples/cxx/minimal.cxx
new file mode 100644
index 0000000..4ab8d02
--- /dev/null
+++ b/examples/cxx/minimal.cxx
@@ -0,0 +1,41 @@
+#include "../../include/rapida.hxx"
+
+/*
+ * \brief Home page route handler.
+ */
+class Home : public rpd::Route {
+protected:
+    /*
+     * \brief Handle GET request.
+     *
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_get(const rpd::Request &req, rpd::Response &res) override
+    {
+        handle_head(req, res);
+
+        /* Unlike the C interface,
+         * the C++ wrapper will call `strdup` for you
+         */
+        res.body("Hello World!");
+    }
+
+    /*
+     * \brief Handle HEAD request.
+     */
+    virtual void handle_head(const rpd::Request &req, rpd::Response &res) override
+    {
+        res.status(rpd_res_st_ok);
+        res.content_type("text/plain");
+    }
+};
+
+int main()
+{
+    rpd::App app("/tmp/webapp.socket");
+
+    app.add_route("/", new Home());
+
+    return app.start();
+}
diff --git a/examples/example-site.nginx.conf b/examples/example-site.nginx.conf
new file mode 100644
index 0000000..8ca7bed
--- /dev/null
+++ b/examples/example-site.nginx.conf
@@ -0,0 +1,11 @@
+server
+{
+    listen 80;
+    server_name localhost;
+
+    location / products
+    {
+        fastcgi_pass unix : / tmp / rapida.example.sock;
+        include fastcgi_params;
+    }
+}
diff --git a/examples/fastcgi_params b/examples/fastcgi_params
new file mode 100644
index 0000000..cd02228
--- /dev/null
+++ b/examples/fastcgi_params
@@ -0,0 +1,21 @@
+fastcgi_param QUERY_STRING $query_string;
+fastcgi_param REQUEST_METHOD $request_method;
+fastcgi_param CONTENT_TYPE $content_type;
+fastcgi_param CONTENT_LENGTH $content_length;
+
+fastcgi_param SCRIPT_NAME $fastcgi_script_name;
+fastcgi_param REQUEST_URI $request_uri;
+fastcgi_param DOCUMENT_URI $document_uri;
+fastcgi_param DOCUMENT_ROOT $document_root;
+fastcgi_param SERVER_PROTOCOL $server_protocol;
+fastcgi_param REQUEST_SCHEME $scheme;
+fastcgi_param HTTPS $https if_not_empty;
+
+fastcgi_param GATEWAY_INTERFACE CGI / 1.1;
+fastcgi_param SERVER_SOFTWARE nginx / $nginx_version;
+
+fastcgi_param REMOTE_ADDR $remote_addr;
+fastcgi_param REMOTE_PORT $remote_port;
+fastcgi_param SERVER_ADDR $server_addr;
+fastcgi_param SERVER_PORT $server_port;
+fastcgi_param SERVER_NAME $server_name;
diff --git a/include/App.hxx b/include/App.hxx
new file mode 100644
index 0000000..2cb3db3
--- /dev/null
+++ b/include/App.hxx
@@ -0,0 +1,65 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_APP_HXX_ENTRY
+#define RAPIDA_APP_HXX_ENTRY
+
+#include "Request.hxx"
+#include "Response.hxx"
+#include "Route.hxx"
+#include "app.h"
+
+namespace rpd {
+/*!
+ * \brief C++ wrapper for Rapida application.
+ */
+class App {
+public:
+    /*!
+     * Creates an rpd app and initializes FastCGI.
+     * \brief Constructor
+     * \param socket_path UNIX Socket path.
+     */
+    App(const char *const socket_path)
+    {
+        rpd_app_create(&app, socket_path);
+    }
+
+    /*!
+     * \brief Starts the requests handling loop.
+     */
+    int start()
+    {
+        return rpd_app_start(&app);
+    }
+
+    /*!
+     * \brief Stops the requests handling loop.
+     */
+    void stop()
+    {
+        app.running = false;
+    }
+
+    /*!
+     * \brief Adds handler for the path.
+     *
+     * \param path Enpoint.
+     * \param route Route handler.
+     */
+    void add_route(const char *const path, Route *route)
+    {
+        rpd_app_add_route(&app, path, &Route::handle_request, route);
+    }
+
+    /*!
+     * \brief Destructor.
+     */
+    virtual ~App() { }
+
+private:
+    rpd_app app; //< Composition with C implementation.
+};
+}
+
+#endif // RAPIDA_APP_HXX_ENTRY
diff --git a/include/KeyVal.hxx b/include/KeyVal.hxx
new file mode 100644
index 0000000..ace50e2
--- /dev/null
+++ b/include/KeyVal.hxx
@@ -0,0 +1,102 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_KEYVAL_HXX_ENTRY
+#define RAPIDA_KEYVAL_HXX_ENTRY
+
+#include "keyval.h"
+
+namespace rpd {
+/*!
+ * \brief C++ wrapper of the key-value pairs storage.
+ */
+class KeyVal {
+public:
+    /*!
+     * \brief Default constructor.
+     *
+     * Create storage without initial allocation.
+     */
+    KeyVal();
+
+    /*!
+     * \brief Constructor.
+     *
+     * \param capacity Initial capacity of this storage.
+     */
+    KeyVal(int capacity);
+
+    /*!
+     * \brief Constructor
+     *
+     * \param keyval Base key-value storage (C implementation).
+     */
+    KeyVal(rpd_keyval *keyval)
+    {
+        _keyval = keyval;
+    }
+
+    /*!
+     * \brief Returns real key-value storage.
+     *
+     * \return C key-value storage.
+     */
+    rpd_keyval *keyval() const
+    {
+        return _keyval;
+    }
+
+    /*!
+     * \brief Get key-value pairs array.
+     *
+     * \return Key-value pairs.
+     */
+    rpd_keyval_item *items() const
+    {
+        return _keyval->items;
+    }
+
+    /*!
+     * \brief Get number of key-value pairs in this storage.
+     *
+     * \return Number of entries.
+     */
+    int size() const
+    {
+        return _keyval->size;
+    }
+
+    /*!
+     * \brief Get capacity of this storage (allocated memory);
+     *
+     * \return Allocated memory.
+     */
+    int capacity() const
+    {
+        return _keyval->capacity;
+    }
+
+    /*!
+     * \brief Get value of key-value pair by it's key.
+     *
+     * \return Value or NULL.
+     */
+    const char *operator[](const char *key)
+    {
+        return rpd_keyval_find(_keyval, key)->val;
+    }
+
+    /*!
+     * \brief Destructor.
+     */
+    virtual ~KeyVal()
+    {
+        rpd_keyval_cleanup(_keyval);
+    }
+
+private:
+    rpd_keyval *_keyval; //< Composition with C implementation.
+};
+}
+
+#endif // RAPIDA_KEYVAL_HXX_ENTRY
diff --git a/include/Query.hxx b/include/Query.hxx
new file mode 100644
index 0000000..8cfbf4b
--- /dev/null
+++ b/include/Query.hxx
@@ -0,0 +1,65 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_QUERY_HXX_ENTRY
+#define RAPIDA_QUERY_HXX_ENTRY
+
+#include "KeyVal.hxx"
+#include "query.h"
+
+namespace rpd {
+/*!
+ * \brief Query storage in key-value format.
+ */
+class Query : public KeyVal {
+public:
+    /*!
+     * \brief Default constructor.
+     *
+     * Just calls parent default costructor.
+     */
+    Query()
+        : KeyVal()
+    {}
+
+    /*!
+     * \brief Constructor.
+     *
+     * \param keyval Key-value storage to base on it.
+     *
+     * Just calls parent constructor with base key-value storage.
+     */
+    Query(rpd_keyval *keyval)
+        : KeyVal(keyval)
+    {}
+
+    /*!
+     * \brief Parse query string into the key-val pairs.
+     *
+     * \param query Query string.
+     *
+     * \return Status code. 0 is success.
+     */
+    int parse(const char *query)
+    {
+        return rpd_query_parse(keyval(), query);
+    }
+
+    /*!
+     * \brief Convert key-val pairs to query string.
+     *
+     * \return Query string.
+     */
+    char *c_str() const
+    {
+        return rpd_query_str(keyval());
+    }
+
+    /*!
+     * \brief Destructor.
+     */
+    virtual ~Query() { }
+};
+}
+
+#endif // RAPIDA_QUERY_HXX_ENTRY
diff --git a/include/Request.hxx b/include/Request.hxx
new file mode 100644
index 0000000..dfa6d94
--- /dev/null
+++ b/include/Request.hxx
@@ -0,0 +1,111 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_REQUEST_HXX_ENTRY
+#define RAPIDA_REQUEST_HXX_ENTRY
+
+#include "Query.hxx"
+#include "request.h"
+
+namespace rpd {
+/*!
+ * \brief C++ request wrapper.
+ */
+class Request {
+public:
+    /*!
+     * \brief Constructor.
+     *
+     * Creates C++ wrapper from original C request.
+     *
+     * \param req C request implementation.
+     */
+    Request(rpd_req *req)
+    {
+        this->req = req;
+    }
+
+    /*!
+     * \brief Gets request method.
+     *
+     * \return Request method.
+     */
+    rpd_req_methods method() const
+    {
+        return req->method;
+    }
+
+    /*!
+     * \brief Gets requested URL.
+     *
+     * \return Request URL.
+     */
+    const rpd_url *path() const
+    {
+        return &req->path;
+    }
+
+    /*!
+     * \brief Gets query parameters.
+     *
+     * \return Query parameters.
+     */
+    Query query() const
+    {
+        return &req->query;
+    }
+
+    /*!
+     * \brief Gets URL parameters.
+     *
+     * If you specify route like <b>/some/:dynamic/route</b>,
+     * middle route segment can be accesed by the _dynamic_ key.
+     *
+     * \return URL parameters as key-value pairs.
+     */
+    KeyVal params() const
+    {
+        return &req->params;
+    }
+
+    /*!
+     * \brief Gets authorization string.
+     *
+     * \return Authorization string.
+     */
+    const char *authorization() const
+    {
+        return req->auth;
+    }
+
+    /*!
+     * \brief Gets cookie string.
+     *
+     * \return Cookie string.
+     */
+    const char *cookie() const
+    {
+        return req->cookie;
+    };
+
+    /*!
+     * \brief Gets request body content.
+     *
+     * \return Body content.
+     */
+    const char *body() const
+    {
+        return req->body;
+    }
+
+    /*!
+     * \brief Destructor.
+     */
+    virtual ~Request() { }
+
+private:
+    rpd_req *req; //< Composition with C implementation.
+};
+}
+
+#endif // RAPIDA_REQUEST_HXX_ENTRY
diff --git a/include/Response.hxx b/include/Response.hxx
new file mode 100644
index 0000000..2b204a8
--- /dev/null
+++ b/include/Response.hxx
@@ -0,0 +1,132 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_RESPONSE_HXX_ENTRY
+#define RAPIDA_RESPONSE_HXX_ENTRY
+
+#include "response.h"
+#include <stdlib.h>
+#include <string.h>
+
+#ifdef EXTENSIONS_INJA
+#include <nlohmann/json.hpp>
+#endif
+
+namespace rpd {
+/*!
+ * \brief C++ response wrapper.
+ */
+class Response {
+public:
+    /*!
+     * \brief Constructor.
+     *
+     * Creates C++ wrapper from original C response.
+     *
+     * \param res C response implementation.
+     */
+    Response(rpd_res *res)
+    {
+        this->res = res;
+    }
+
+    /*!
+     * \brief Sets response status code.
+     *
+     * See rpd_res_statuses enumeration.
+     *
+     * \param status Status code.
+     */
+    void status(rpd_res_statuses status)
+    {
+        res->status = status;
+    }
+
+    /*!
+     * \brief Sets response status code.
+     *
+     * Sets numbered status code.
+     * May be useful when needed status code is
+     * unavailable in rpd_res_status.
+     *
+     * If not, please, use enumeration.
+     *
+     * \param status Status code.
+     */
+    void status(long status)
+    {
+        res->status = static_cast<rpd_res_statuses>(status);
+    }
+
+    /*!
+     * \brief Sets _location_ response field.
+     *
+     * \param location Location URL.
+     */
+    void location(const char *location)
+    {
+        if (res->location)
+            free(res->location);
+        res->location = strdup(location);
+    }
+
+    /*!
+     * \brief Sets _Content-Type_ response field.
+     *
+     * \param content_type Response content type.
+     */
+    void content_type(const char *content_type)
+    {
+        if (res->content_type)
+            free(res->content_type);
+        res->content_type = strdup(content_type);
+    }
+
+    /*!
+     * \brief Sets cookie field.
+     *
+     * Adds new cookie field to key-value storage.
+     * If you need to set cookie parameters such as lifetime,
+     * place it to val.
+     *
+     * \param key Cookie field key.
+     * \param val Cookie field value.
+     */
+    void cookie(const char *key, const char *val)
+    {
+        rpd_keyval_insert(&res->cookie, key, val);
+    }
+
+    /*!
+     * \brief Sets response body.
+     *
+     * \param body Response body.
+     */
+    void body(const char *body)
+    {
+        if (res->body)
+            free(res->body);
+        res->body = strdup(body);
+    }
+
+#ifdef EXTENSIONS_INJA
+    /*!
+     * \brief Render data to HTML template.
+     * \param path Path to HTML template relative to dist location.
+     * \param data Template data to interpolate.
+     * \param out  FastCGI output stream.
+     */
+    void render(const char *path, nlohmann::json data);
+#endif
+
+    /*!
+     * \brief Destructor.
+     */
+    virtual ~Response() { }
+
+private:
+    rpd_res *res; //< Composition with C implementation.
+};
+}
+
+#endif // RAPIDA_RESPONSE_HXX_ENTRY
diff --git a/include/Route.hxx b/include/Route.hxx
new file mode 100644
index 0000000..682b167
--- /dev/null
+++ b/include/Route.hxx
@@ -0,0 +1,139 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_ROUTE_HXX_ENTRY
+#define RAPIDA_ROUTE_HXX_ENTRY
+
+#include "Request.hxx"
+#include "Response.hxx"
+
+namespace rpd {
+/*!
+ * \brief Base class for routes.
+ */
+class Route {
+public:
+    /*!
+     * \brief Default constructor.
+     *
+     * Creates a new route to handle roquests.
+     */
+    Route() { }
+
+    /*!
+     * \brief Client request handler.
+     *
+     * Reads the request method and calls handler for this method.
+     * \see handle_get for GET requests.
+     * \see handle_post for POST requests.
+     * \see handle_put for PUT requests.
+     * etc.
+     *
+     * \note This method will be automatically called.
+     *       You don't need to use it.
+     *
+     * \param req Request instance.
+     * \param res Response instance.
+     * \param route C rpd_route instance.
+     */
+    static void handle_request(rpd_req *req, rpd_res *res, void *route);
+
+    /*!
+     * \brief Destructor.
+     */
+    virtual ~Route() { }
+
+protected:
+    /*!
+     * \brief GET request handler.
+     *
+     * Derived class should override this method.
+     *
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_get(const Request &req, Response &res) = 0;
+
+    /*!
+     * \brief HEAD request handler.
+     *
+     * Derived class should override this method.
+     *
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_head(const Request &req, Response &res) = 0;
+
+    /*!
+     * \brief POST request handler.
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_post(const Request &req, Response &res)
+    {
+        res.status(rpd_res_st_not_implemented);
+    }
+
+    /*!
+     * \brief PUT request handler.
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_put(const Request &req, Response &res)
+    {
+        res.status(rpd_res_st_not_implemented);
+    }
+
+    /*!
+     * \brief DELETE request handler.
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_delete(const Request &req, Response &res)
+    {
+        res.status(rpd_res_st_not_implemented);
+    }
+
+    /*!
+     * \brief CONNECT request handler.
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_connect(const Request &req, Response &res)
+    {
+        res.status(rpd_res_st_not_implemented);
+    }
+
+    /*!
+     * \brief OPTIONS request handler.
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_options(const Request &req, Response &res)
+    {
+        res.status(rpd_res_st_not_implemented);
+    }
+
+    /*!
+     * \brief TRACE request handler.
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_trace(const Request &req, Response &res)
+    {
+        res.status(rpd_res_st_not_implemented);
+    }
+
+    /*!
+     * \brief PATCH request handler.
+     * \param req Request.
+     * \param res Response.
+     */
+    virtual void handle_patch(const Request &req, Response &res)
+    {
+        res.status(rpd_res_st_not_implemented);
+    }
+};
+}
+
+#endif // RAPIDA_ROUTE_HXX_ENTRY
diff --git a/include/Url.hxx b/include/Url.hxx
new file mode 100644
index 0000000..d81a1dd
--- /dev/null
+++ b/include/Url.hxx
@@ -0,0 +1,78 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_URL_HXX_ENTRY
+#define RAPIDA_URL_HXX_ENTRY
+
+#include "url.h"
+
+namespace rpd {
+/*!
+ * \brief C++ URL wrapper.
+ */
+class Url {
+public:
+    /*!
+     * \brief Default constructor.
+     *
+     * Initializes URL with null values.
+     */
+    Url()
+    {
+        url.parts = NULL;
+        url.parts_len = 0;
+    }
+
+    /*!
+     * \brief Constructor.
+     */
+    Url(const char *url) { parse(url); }
+
+    /*!
+     * \brief Parse URL.
+     *
+     * \param url URL.
+     *
+     * \return Status code. A non-zero value is an error.
+     */
+    int parse(const char *url)
+    {
+        return rpd_url_parse(&this->url, url);
+    }
+
+    /*!
+     * \brief Get number of URL parts.
+     *
+     * \return Number of URL parts.
+     */
+    int length() const
+    {
+        return url.parts_len;
+    }
+
+    /*!
+     * \brief Get URL part at index.
+     *
+     * \param idx Index of the URL part.
+     *
+     * \return URL part.
+     */
+    const char *operator[](int idx)
+    {
+        return url.parts[idx];
+    }
+
+    /*!
+     * \brief Destructor.
+     */
+    virtual ~Url()
+    {
+        rpd_url_cleanup(&url);
+    }
+
+private:
+    rpd_url url; //< Composition with C implementation.
+};
+}
+
+#endif // RAPIDA_URL_HXX_ENTRY
diff --git a/include/app.h b/include/app.h
new file mode 100644
index 0000000..adf4666
--- /dev/null
+++ b/include/app.h
@@ -0,0 +1,67 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file app.h
+ * \brief Rapida application
+ */
+#ifndef RAPIDA_APP_H_ENTRY
+#define RAPIDA_APP_H_ENTRY
+
+#include "route.h"
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/*!
+ * \brief Rapida application main struct.
+ */
+typedef struct {
+    int running; /**< Application will be running while this flag is true. */
+    const char *sock_path; /**< Application UNIX Socket path. */
+    int sock_id; /**< Application UNIX Socket id. */
+    int routes_len; /**< Length of the rpd_app::routes array. */
+    rpd_route *routes; /**< Array of the active routes. */
+} rpd_app;
+
+/*!
+ * \brief Creates Rapida application.
+ *
+ * \param app Pointer to application instance.
+ * \param sock_path UNIX Socket path.
+ *
+ * \return Status. 0 is success.
+ */
+int rpd_app_create(rpd_app *app, const char *sock_path);
+
+/*!
+ * \brief Starts Rapida main loop.
+ * \param app Application instance.
+ *
+ * \return Status. 0 is success.
+ */
+int rpd_app_start(rpd_app *app);
+
+/*!
+ * \brief Adds route to application.
+ *
+ * It's better to add routes before application start,
+ * because rpd_app::routes when you add new route
+ * rpd_app::routes will be reallocated.
+ *
+ * \param app      Application instance.
+ * \param path     Path to handle.
+ * \param cb       Handling callback.
+ * \param userdata Additional data to pass to cb.
+ *
+ * \return Status. 0 is success.
+ */
+int rpd_app_add_route(rpd_app *app, const char *path, rpd_route_cb cb,
+    void *userdata);
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif // RAPIDA_APP_H_ENTRY
diff --git a/include/keyval.h b/include/keyval.h
new file mode 100644
index 0000000..60c270b
--- /dev/null
+++ b/include/keyval.h
@@ -0,0 +1,92 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file keyval.h
+ * \brief Simple key-value struct based on an array
+ * to store query strings, dynamic parameters, etc.
+ */
+#ifndef RAPIDA_KEYVAL_H_ENTRY
+#define RAPIDA_KEYVAL_H_ENTRY
+
+#include "unistd.h"
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/*!
+ * \brief Key-value pair.
+ */
+typedef struct {
+    char *key; /**< Key */
+    char *val; /**< Value */
+} rpd_keyval_item;
+
+/*!
+ * \brief Key-value pairs storage.
+ */
+typedef struct {
+    rpd_keyval_item *items; /**< Key-value pairs array. */
+    int size; /**< Number of elements in rpd_keyval::items. */
+    int capacity; /**< Current capacity (allocated memory). */
+} rpd_keyval;
+
+/*!
+ * \brief Initialize the rpd_keyval instance.
+ *
+ * \param keyval Key-value storage instance.
+ * \param capacity Initial capacity of the keyval storage.
+ *                 Set it to 0 if you don't need initial allocation.
+ *
+ * \return Status code.
+ */
+int rpd_keyval_init(rpd_keyval *keyval, int capacity);
+
+/*!
+ * \brief Insert new key-value pair into the storage.
+ *
+ * If size of the storage is equal to it's capacity, this function firstly
+ * will reallocate rpd_keyval::items.
+ *
+ * \param keyval Key-value storage.
+ * \param key New pair key.
+ * \param value New pair value.
+ *
+ * \return Status code.
+ * `0`: Success.
+ * `1`: Out of memory when reallocate rpd_keyval::items to new capacity.
+ * `2`: Failed to duplicate rpd_keyval_insert::key or rpd_keyval_insert::value.
+ */
+int rpd_keyval_insert(rpd_keyval *keyval, const char *key, const char *value);
+
+/*!
+ * \brief Finds key-value pair by it's key.
+ *
+ * \param keyval Key-value storage instance.
+ * \param key Key to search.
+ *
+ * \return Found item or NULL.
+ */
+rpd_keyval_item *rpd_keyval_find(const rpd_keyval *keyval, const char *key);
+
+/*!
+ * \brief Free key-val pairs and reset.
+ *
+ * This function don't will free rpd_keyval::items memory,
+ * so capacity will be saved.
+ * And also this function doesn't free keyval itself.
+ * You can do it manually.
+ *
+ * :note: This is done so that you can use keyval in stack,
+ * also it minimize system calls to allocate memory.
+ *
+ * \param keyval Key-value storage.
+ */
+void rpd_keyval_cleanup(rpd_keyval *keyval);
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif /* RAPIDA_KEYVAL_H_ENTRY */
diff --git a/include/query.h b/include/query.h
new file mode 100644
index 0000000..bf623fc
--- /dev/null
+++ b/include/query.h
@@ -0,0 +1,42 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file query.h
+ * \brief Query string processing.
+ */
+#ifndef RAPIDA_QUERY_H_ENTRY
+#define RAPIDA_QUERY_H_ENTRY
+
+#include "keyval.h"
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/*!
+ * \brief Parses a query string.
+ *
+ * Parses a query string like `param=val&param1=val1` into an rpd_query struct.
+ *
+ * \param dest The rpd_keyval instance to write the parsed query.
+ * \param query The source query string to parse.
+ *
+ * \return Status code. A non-zero value is an error.
+ */
+int rpd_query_parse(rpd_keyval *dest, const char *query);
+
+/*!
+ * \brief Creates query string from query instance.
+ *
+ * \param query Query instance.
+ *
+ * \return Query string.
+ */
+char *rpd_query_str(const rpd_keyval *query);
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif /* RAPIDA_QUERY_H_ENTRY */
diff --git a/include/rapida.h b/include/rapida.h
new file mode 100644
index 0000000..1657a14
--- /dev/null
+++ b/include/rapida.h
@@ -0,0 +1,15 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file rapida.h
+ * \brief Common C interface header of the Rapida.
+ */
+#ifndef RAPIDA_H_ENTRY
+#define RAPIDA_H_ENTRY
+
+#include "app.h"
+#include "query.h"
+#include "url.h"
+
+#endif /* RAPIDA_H_ENTRY */
diff --git a/include/rapida.hxx b/include/rapida.hxx
new file mode 100644
index 0000000..1930785
--- /dev/null
+++ b/include/rapida.hxx
@@ -0,0 +1,13 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/// \file rapida.hxx C++ interface header of the Rapida.
+#ifndef RAPIDA_HXX_ENTRY
+#define RAPIDA_HXX_ENTRY
+
+#include "App.hxx"
+#include "Request.hxx"
+#include "Response.hxx"
+#include "Route.hxx"
+
+#endif // RAPIDA_HXX_ENTRY
diff --git a/include/request.h b/include/request.h
new file mode 100644
index 0000000..c47d736
--- /dev/null
+++ b/include/request.h
@@ -0,0 +1,72 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file request.h
+ * \brief Request.
+ */
+#ifndef RAPIDA_REQUEST_H_ENTRY
+#define RAPIDA_REQUEST_H_ENTRY
+
+#include "query.h"
+#include "url.h"
+#include <fcgiapp.h>
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/*!
+ * \brief Request method types.
+ */
+enum rpd_req_methods {
+    UNKNOWN = 0,
+    GET,
+    HEAD,
+    POST,
+    PUT,
+    DELETE,
+    CONNECT,
+    OPTIONS,
+    TRACE,
+    PATCH
+};
+
+/*!
+ * \brief Request struct.
+ */
+typedef struct {
+    enum rpd_req_methods method; /**< Request method. */
+    char *auth; /**< Authorization field. */
+    char *cookie; /**< Cookie field. */
+    char *body; /**< Body field. */
+    rpd_url path; /**< Requested URL. */
+    rpd_keyval query; /**< Query. */
+    rpd_keyval params; /**< Dynamic parameters. */
+} rpd_req;
+
+int rpd_req_parse(rpd_req *dest, FCGX_Request *req);
+
+/*!
+ * \brief Parser string request method to enumeration value.
+ *
+ * \param method Request method string.
+ *
+ * \return Request method.
+ */
+enum rpd_req_methods rpd_req_smethod(const char *method);
+
+/*!
+ * \brief Cleans request data.
+ *
+ * Request instance will not be freed, only it's data.
+ *
+ * \param req Request instance.
+ */
+void rpd_req_cleanup(rpd_req *req);
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif /* RAPIDA_REQUEST_H_ENTRY */
diff --git a/include/response.h b/include/response.h
new file mode 100644
index 0000000..b407276
--- /dev/null
+++ b/include/response.h
@@ -0,0 +1,124 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file response.h
+ * \brief Response.
+ */
+#ifndef RAPIDA_RESPONSE_H_ENTRY
+#define RAPIDA_RESPONSE_H_ENTRY
+
+#include "keyval.h"
+#include <fcgiapp.h>
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/*!
+ * \brief Response statuses.
+ */
+enum rpd_res_statuses {
+    rpd_res_st_continue = 100,
+    rpd_res_st_switching_protocols = 101,
+
+    /*! Experimental, check browser compatibility */
+    rpd_res_st_early_hints = 103,
+
+    rpd_res_st_ok = 200,
+    rpd_res_st_created = 201,
+    rpd_res_st_accepted = 202,
+    rpd_res_st_non_authoritative_info = 203,
+    rpd_res_st_no_content = 204,
+    rpd_res_st_reset_content = 205,
+    rpd_res_st_partial_content = 206,
+
+    rpd_res_st_multiple_choices = 300,
+    rpd_res_st_moved_permanently = 301,
+    rpd_res_st_found = 302,
+    rpd_res_st_see_other = 303,
+    rpd_res_st_not_modified = 304,
+    rpd_res_st_temp_redirect = 307,
+    rpd_res_st_perm_redirect = 308,
+
+    rpd_res_st_bad_request = 400,
+    rpd_res_st_unauthorized = 401,
+    rpd_res_st_payment_required = 402,
+    rpd_res_st_forbidden = 403,
+    rpd_res_st_not_found = 404,
+    rpd_res_st_method_not_allowed = 405,
+    rpd_res_st_not_acceptable = 406,
+    rpd_res_st_proxy_auth_required = 407,
+    rpd_res_st_req_timeout = 408,
+    rpd_res_st_conflict = 409,
+    rpd_res_st_gone = 410,
+    rpd_res_st_length_required = 411,
+    rpd_res_st_precondition_failed = 412,
+    rpd_res_st_payload_too_large = 413,
+    rpd_res_st_uri_too_long = 414,
+    rpd_res_st_unsupported_media_type = 415,
+    rpd_res_st_range_not_satisfiable = 416,
+    rpd_res_st_expectation_failed = 417,
+    rpd_res_st_i_am_teapot = 418,
+    rpd_res_st_unprocessable_entity = 422,
+    rpd_res_st_too_early = 425,
+    rpd_res_st_upgrade_required = 426,
+    rpd_res_st_precondition_required = 428,
+    rpd_res_st_too_many_requests = 429,
+    rpd_res_st_request_header_fields_too_large = 431,
+    rpd_res_st_unavailable_for_legal_reasons = 451,
+
+    rpd_res_st_internal_server_error = 500,
+    rpd_res_st_not_implemented = 501,
+    rpd_res_st_bad_gateway = 502,
+    rpd_res_st_service_unavailable = 503,
+    rpd_res_st_gateway_timeout = 504,
+    rpd_res_st_http_ver_not_supported = 505,
+    rpd_res_st_variant_also_negotiates = 506,
+    rpd_res_st_insufficient_storage = 507,
+    rpd_res_st_loop_detected = 508,
+    rpd_res_st_not_extended = 510,
+    rpd_res_st_network_auth_required = 511
+};
+
+/*!
+ * \brief Response data wich will be sent to client.
+ */
+typedef struct {
+    enum rpd_res_statuses status; /**< Response status code. */
+    FCGX_Stream *out; /**< Output stream. */
+    char *location; /**< Location field. */
+    char *content_type; /**< Content type. */
+    char *body; /**< Response body. */
+    rpd_keyval cookie; /**< Set-Cookie fields. */
+} rpd_res;
+
+/*!
+ * \brief Initialize response data from FastCGI request.
+ *
+ * \param dest Response instance.
+ * \param req FastCGI request.
+ */
+void rpd_res_init(rpd_res *dest, FCGX_Request *req);
+
+/*!
+ * \brief Sends response to client.
+ * \param res Response instance.
+ */
+int rpd_res_send(rpd_res *res);
+
+/*!
+ * \brief Cleans response instance.
+ *
+ * This function will not frees response instance,
+ * only it's data.
+ *
+ * \param res Response instance to cleanup.
+ */
+void rpd_res_cleanup(rpd_res *res);
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif /* RAPIDA_RESPONSE_H_ENTRY */
diff --git a/include/route.h b/include/route.h
new file mode 100644
index 0000000..1e25500
--- /dev/null
+++ b/include/route.h
@@ -0,0 +1,54 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file route.h
+ * \brief Route handler.
+ */
+#ifndef RAPIDA_ROUTE_H_ENTRY
+#define RAPIDA_ROUTE_H_ENTRY
+
+#include "request.h"
+#include "response.h"
+#include "url.h"
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/*!
+ * \brief Request handling callback type.
+ *
+ * \param req Resquest.
+ * \param res Response.
+ * \param userdata User data.
+ */
+typedef void (*rpd_route_cb)(rpd_req *req, rpd_res *res, void *userdata);
+
+/*!
+ * \brief Route struct.
+ */
+typedef struct {
+    rpd_url path; /**< Route path. */
+    rpd_route_cb cb; /**< Callback. */
+    void *userdata; /**< User data */
+} rpd_route;
+
+/*!
+ * \brief Fills route instance.
+ *
+ * \param dest Route instance.
+ * \param path Route path.
+ * \param cb   Handling callback.
+ * \param userdata Additional callback data.
+ *
+ * \return Status. 0 is success.
+ */
+int rpd_route_init(rpd_route *dest, const char *path, rpd_route_cb cb,
+    void *userdata);
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif /* RAPIDA_ROUTE_H_ENTRY */
diff --git a/include/url.h b/include/url.h
new file mode 100644
index 0000000..2fa119e
--- /dev/null
+++ b/include/url.h
@@ -0,0 +1,72 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+/*!
+ * \file url.h
+ * \brief Processing URLs.
+ */
+#ifndef RAPIDA_URL_H_ENTRY
+#define RAPIDA_URL_H_ENTRY
+
+#include "keyval.h"
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/*!
+ * \brief URL.
+ */
+typedef struct {
+    /*! An array of URL parts. */
+    char **parts;
+    int parts_len; /**< The length of rpd_url::parts. */
+} rpd_url;
+
+/*!
+ * \brief Parses URL.
+ *
+ * If your rpd_url instance was already filled, first free it **fields**.
+ * rpd_url_parse::src will be dupblicated using the `strdup`,
+ * so you can free source string.
+ *
+ * \param dest rpd_url instance where parsed data will be placed.
+ * \param src Source URL string.
+ *
+ * \return Status code. A non-zero value is an error.
+ */
+int rpd_url_parse(rpd_url *dest, const char *src);
+
+/*!
+ * \brief Cleanup URL instance.
+ *
+ * \param url URL instance.
+ */
+void rpd_url_cleanup(rpd_url *url);
+
+/*!
+ * \brief Parse dynamic parameters keys into key-value pairs.
+ *
+ * \param dest Key-value storage instance.
+ * \param tpl  URL with dynamic parameters identifiers.
+ *
+ * \return Status. 0 is success.
+ */
+int rpd_url_params_parse_keys(rpd_keyval *dest, const rpd_url *tpl);
+
+/*!
+ * \brief Parse dynamic parameters values into key-value pairs.
+ *
+ * \param dest Key-value storage with parsed keys.
+ * \param url URL.
+ * \param tpl URL with dynamic parameters identifiers.
+ *
+ * \return Status. 0 is success.
+ */
+int rpd_url_params_parse_vals(rpd_keyval *dest, const rpd_url *url, const rpd_url *tpl);
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif /* RAPIDA_URL_H_ENTRY */
diff --git a/tests/app.cxx b/tests/app.cxx
new file mode 100644
index 0000000..e49e2b5
--- /dev/null
+++ b/tests/app.cxx
@@ -0,0 +1,26 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "app.h"
+#include "tests.hxx"
+
+using namespace rpd;
+
+TEST_CASE("Application")
+{
+    rpd_app app;
+    int res = rpd_app_create(&app, "/tmp/rapida.test.socket");
+
+    SECTION("App creation")
+    {
+        REQUIRE(res == 0);
+    }
+
+    SECTION("Adding route")
+    {
+        auto handle = [](rpd_req *req, rpd_res *res, void *userdata) {};
+        REQUIRE(rpd_app_add_route(&app, "/", handle, NULL) == 0);
+        REQUIRE(app.routes_len == 1);
+        REQUIRE(app.routes != NULL);
+    }
+}
diff --git a/tests/keyval.cxx b/tests/keyval.cxx
new file mode 100644
index 0000000..a217efe
--- /dev/null
+++ b/tests/keyval.cxx
@@ -0,0 +1,44 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "keyval.h"
+#include "tests.hxx"
+
+using namespace rpd;
+
+TEST_CASE("Key-value storage")
+{
+    rpd_keyval keyval;
+    rpd_keyval_init(&keyval, 10);
+
+    SECTION("Initializing")
+    {
+        rpd_keyval_init(&keyval, 10);
+        REQUIRE(keyval.size == 0);
+        REQUIRE(keyval.capacity == 10);
+    }
+
+    SECTION("Inserting")
+    {
+        REQUIRE(rpd_keyval_insert(&keyval, "key", "val") == 0);
+        REQUIRE(keyval.size == 1);
+        REQUIRE(std::string(keyval.items[0].key) == "key");
+        REQUIRE(std::string(keyval.items[0].val) == "val");
+    }
+
+    SECTION("Search")
+    {
+        int sz = keyval.size;
+        REQUIRE(rpd_keyval_insert(&keyval, "key1", "val") == 0);
+        REQUIRE(keyval.size == sz + 1);
+        rpd_keyval_item *item = rpd_keyval_find(&keyval, "key1");
+        REQUIRE(item != NULL);
+        REQUIRE(std::string(item->val) == "val");
+    }
+
+    SECTION("Cleanup")
+    {
+        rpd_keyval_cleanup(&keyval);
+        REQUIRE(keyval.size == 0);
+    }
+}
diff --git a/tests/query.cxx b/tests/query.cxx
new file mode 100644
index 0000000..c368e66
--- /dev/null
+++ b/tests/query.cxx
@@ -0,0 +1,80 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "tests.hxx"
+
+using namespace rpd;
+
+TEST_CASE("Query string parsing")
+{
+    rpd_keyval query;
+    rpd_keyval_init(&query, 0);
+
+    SECTION("Query initialization")
+    {
+        rpd_keyval q;
+        rpd_keyval_init(&q, 0);
+
+        REQUIRE(q.capacity == 0);
+        REQUIRE(q.size == 0);
+        REQUIRE(q.items == NULL);
+    }
+
+    SECTION("param=val query should be parsed into key=param and val=val")
+    {
+        REQUIRE(rpd_query_parse(&query, "param=val") == 0);
+        REQUIRE(query.size == 1);
+        REQUIRE(std::string(query.items[0].key) == "param");
+        REQUIRE(std::string(query.items[0].val) == "val");
+    }
+
+    SECTION("Parameter with empty value should be NULL")
+    {
+        REQUIRE(rpd_query_parse(&query, "param=") == 0);
+        REQUIRE(query.size == 1);
+        REQUIRE(std::string(query.items[0].key) == "param");
+        REQUIRE(query.items[0].val == NULL);
+    }
+
+    SECTION("Empty parameter with value should be ignored")
+    {
+        REQUIRE(rpd_query_parse(&query, "=val") == 0);
+        REQUIRE(query.size == 0);
+    }
+
+    SECTION("Complex test with all situations")
+    {
+        REQUIRE(rpd_query_parse(&query, "param=val&param1=&=val2") == 0);
+        REQUIRE(query.size == 2);
+        REQUIRE(std::string(query.items[0].key) == "param");
+        REQUIRE(std::string(query.items[0].val) == "val");
+        REQUIRE(std::string(query.items[1].key) == "param1");
+        REQUIRE(query.items[1].val == NULL);
+        REQUIRE(std::string(rpd_query_str(&query)) == "param=val");
+    }
+
+    SECTION("C++ query wrapper initialization")
+    {
+        Query cxxquery;
+
+        REQUIRE(cxxquery.capacity() == 0);
+        REQUIRE(cxxquery.size() == 0);
+        REQUIRE(cxxquery.items() == NULL);
+    }
+
+    SECTION("Complex test with Query C++ wrapper")
+    {
+        Query cxxquery;
+        const char *qstr = "param=val&param1=&=val2";
+
+        REQUIRE(cxxquery.parse(qstr) == 0);
+        REQUIRE(cxxquery.size() == 2);
+        REQUIRE(std::string(cxxquery["param"]) == "val");
+        REQUIRE(cxxquery["param1"] == NULL);
+    }
+
+    rpd_keyval_cleanup(&query);
+    if (query.items) {
+        free(query.items);
+    }
+}
diff --git a/tests/tests.cxx b/tests/tests.cxx
new file mode 100644
index 0000000..a617fe9
--- /dev/null
+++ b/tests/tests.cxx
@@ -0,0 +1,5 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#define CATCH_CONFIG_MAIN
+#include "tests.hxx"
diff --git a/tests/tests.hxx b/tests/tests.hxx
new file mode 100644
index 0000000..47ee70c
--- /dev/null
+++ b/tests/tests.hxx
@@ -0,0 +1,11 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#ifndef RAPIDA_TESTS_HXX_ENTRY
+#define RAPIDA_TESTS_HXX_ENTRY
+
+#include "rapida.h"
+#include "rapida.hxx"
+#include <catch2/catch.hpp>
+
+#endif // RAPIDA_TESTS_HXX_ENTRY
diff --git a/tests/url.cxx b/tests/url.cxx
new file mode 100644
index 0000000..248e3f3
--- /dev/null
+++ b/tests/url.cxx
@@ -0,0 +1,59 @@
+/* SPDX-License-Identifier: GPL-3.0-or-later */
+/* Copyright 2022 Ivan Polyakov */
+
+#include "Url.hxx"
+#include "tests.hxx"
+
+using namespace rpd;
+
+TEST_CASE("URL processing")
+{
+    rpd_url url { NULL, 0 };
+
+    SECTION("\"/some/route\" parsing")
+    {
+        REQUIRE(rpd_url_parse(&url, "/some/route") == 0);
+        REQUIRE(url.parts_len == 2);
+        REQUIRE(std::string(url.parts[0]) == "some");
+        REQUIRE(std::string(url.parts[1]) == "route");
+    }
+
+    SECTION("Invalid route without slashes should be ignored")
+    {
+        REQUIRE(rpd_url_parse(&url, "someroute") == 0);
+        REQUIRE(url.parts_len == 0);
+    }
+
+    SECTION("Empty part (\"//\") in the routes should be ignored")
+    {
+        REQUIRE(rpd_url_parse(&url, "/some//route/") == 0);
+        REQUIRE(url.parts_len == 2);
+        REQUIRE(std::string(url.parts[0]) == "some");
+        REQUIRE(std::string(url.parts[1]) == "route");
+    }
+
+    SECTION("Dynamic parameters should be saved")
+    {
+        REQUIRE(rpd_url_parse(&url, "/some/:param") == 0);
+        REQUIRE(url.parts_len == 2);
+        REQUIRE(std::string(url.parts[0]) == "some");
+        REQUIRE(std::string(url.parts[1]) == ":param");
+    }
+
+    SECTION("Test valid route using the C++ wrapper")
+    {
+        Url cxxurl;
+        REQUIRE(cxxurl.parse("/some/route") == 0);
+        REQUIRE(cxxurl.length() == 2);
+        REQUIRE(std::string(cxxurl[0]) == "some");
+        REQUIRE(std::string(cxxurl[1]) == "route");
+    }
+
+    SECTION("Cleaning")
+    {
+        rpd_url_parse(&url, "/some/route");
+        rpd_url_cleanup(&url);
+        REQUIRE(url.parts_len == 0);
+        REQUIRE(url.parts == 0);
+    }
+}