{
    "": "In conclusion, this representation for the message container is well thought out, provides comprehensive flexibility, and avoids the necessity of defining additional traits classes. User declarations of functions that accept headers or messages as parameters are easy to write in a variety of ways to accomplish different results, without forcing cumbersome SFINAE declarations everywhere.",
    "126": "};",
    "138": "}; ```",
    "192": "};",
    "194": "/// An HTTP response header template<class Fields> struct header<false, Fields> : Fields {",
    "201": "};",
    "211": "};",
    "269": "};",
    "271": "/// An HTTP response header template<class Fields> struct header<false, Fields> : Fields {",
    "279": "}; ```",
    "312": "}; ```"
}