HttpMessage class abstract interface

Represents the base abstraction for HTTP messages, containing both headers and a potential body.

This interface is the common parent for both HttpInputMessage (used for requests) and HttpOutputMessage (used for responses). It provides the fundamental contract that all HTTP message types must implement, ensuring consistent access to message headers across different message contexts.

Responsibilities

• Provides access to the HTTP HttpHeaders
• Defines a common contract for input/output message structures
• Serves as a foundation for high-level entities like RequestHttpBody and ResponseBody
• Enables header manipulation and inspection regardless of message direction

Inheritance Hierarchy

HttpMessage (abstract)
├── HttpInputMessage (abstract) - for incoming messages
└── HttpOutputMessage (abstract) - for outgoing messages

Example

void logHeaders(HttpMessage message) {
  final headers = message.getHeaders();
  headers.forEach((name, values) {
    print('$name: ${values.join(", ")}');
  });
}

Design Notes

• Part of JetLeaf's unified request/response abstraction model
• Does not itself define a body; see HttpInputMessage and HttpOutputMessage for body access
• Designed to be implemented by both client and server-side message types

Related Classes

• HttpInputMessage - For reading incoming HTTP messages
• HttpOutputMessage - For writing outgoing HTTP messages
• HttpHeaders - Header storage and manipulation
• RequestHttpBody - High-level request representation
• ResponseBody - High-level response representation