Refactory protocol to set X-Event-Content based on content length
Otoru opened this issue · comments
In the current code, we use an queue to store headers of api-response event and add the content before put on the events queue.
The proposal is use a Content-Length
headers to read a content of a StreamReader and set the X-Event-Content without auxiliar queues or filters based on content-type.
We need create tests to validate behavior of protocol with api-response events and generic events.