MNENetprotocolHandler: Define interface methods to return header data in a generic format #6

Closed
opened 2 years ago by ncc1988 · 3 comments
ncc1988 commented 2 years ago
Owner

The format should be as generic as possible.

The format should be as generic as possible.
ncc1988 self-assigned this 2 years ago
ncc1988 added this to the Version 0.0.1 - "Uyghur lives matter!" milestone 2 years ago
Poster
Owner

To implement this, a Request and Response class shall be added: #9

~~To implement this, a Request and Response class shall be added: #9~~
Poster
Owner

To implement this, the work in #9 must be completed. The result will be an interface for response header handlers that get header data in a generic format.

To implement this, the work in #9 must be completed. The result will be an interface for response header handlers that get header data in a generic format.
ncc1988 added a new dependency 2 years ago
ncc1988 added the
TODO
label 11 months ago
ncc1988 added the
enhancement
label 11 months ago
Poster
Owner

Since header data are protocol dependent, defining an unified format for returning them seems to be problematic.

HTTPRequest already has the addRequestHeader and getResponseHeader methods to set header fields for a request and get the whole response header as std::unordered_map.

Since header data are protocol dependent, defining an unified format for returning them seems to be problematic. HTTPRequest already has the addRequestHeader and getResponseHeader methods to set header fields for a request and get the whole response header as std::unordered_map.
ncc1988 removed the
TODO
label 9 months ago
ncc1988 closed this issue 9 months ago
Sign in to join this conversation.
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Loading…
There is no content yet.