Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Labels:None
Description
In the AWDIP sample HTTP WFS request the HTTP communication is completely outside of DuckHawk. The request gets set up within the testing function, and if you want to get the response data, it would also be within that function.
A tighter integration with DuckHawk is needed, so the listeners can make use out of the whole parameters (host, port, path, request etc) and the response data (header, body etc).
I just figured out that getting the response to the listeners is easily possible with the already implemented properties.