bmcweb/docs/HEADERS.md

7 bmcweb at one point was a crow-based project. Evidence of this can still be seen
13 Boost::beast at the time we ported took the same opinion, relying on header
15 time is taken up in boost::beast template instantiations, specifically for
20 implemented 3-4 times in the project, the latest of which is below. The intent
27 making total compilation slower, not faster, as the slowest-to-compile parts end
28 up getting compiled multiple times, then the duplicates deleted at link time.
34 - Moving the Request and Response containers to opaque structures, so a majority
40   pursued by maintainers over time.
41 - Moving the internals of Request/Response/Connection to rely on something like
44   time templates, and might not require abstracting the Request/Response
46 - Reduce the bmcweb binary size to the point where link time optimization is not
47   required for most usages. About half of the bmcweb build time is spent doing
48   link time optimization, which, as of this time is required to keep bmcweb code
49   small enough to deploy on an actual BMCs (See DEVELOPING.md for details). One