This event is fired as a reaction to {@link ProcessHttpRequest} for every request that should be processed by Warp.
Requests that should not be processed by Warp fires {@link ProcessHttpRequest} but their processing needs to be separated andso they do not fire {@link ProcessWarpRequest}.
As a reaction to this event, Warp implementation should fire {@link ExecuteWarp} event and then watch for Warp executionresult - in this stage Warp guards all exception that may arise from processing and finally it waits for result of the test. Finally it saves this result so that it can be retrieved by Warp Client.
@see ExecuteWarp @see ProcessHttpRequest
|
|