[arquillian-issues] [JBoss JIRA] (ARQ-1325) Warp: replace piggy-backing on request/response with direct test->filter communication

[Lukáš Fryč (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ARQ-1325 started by Lukáš Fryč.

> Warp: replace piggy-backing on request/response with direct test->filter communication
> --------------------------------------------------------------------------------------
>
>                 Key: ARQ-1325
>                 URL: https://issues.jboss.org/browse/ARQ-1325
>             Project: Arquillian
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Warp
>            Reporter: Lukáš Fryč
>            Assignee: Lukáš Fryč
>            Priority: Critical
>             Fix For: warp_1.0.0.Alpha3
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We can do similar processing as we did with CommandService here:
> https://github.com/arquillian/arquillian-extension-warp/blob/aa0745237f5df939af587c7f4682c441299713ca/impl/src/main/java/org/jboss/arquillian/warp/impl/server/execution/WarpFilter.java#L93
> The CommandService communicates with the WarpFilter asynchronously and its requests are not processed directly, they delegates to the request-serving routine.
> ----
> This way, Warp could:
> 0. request is issued against proxy
> 1. catch the request on the proxy
> 2. register the RequestPayload (with Inspection) in the registry via the WarpFilter (under generated request-specific UUID)
> 3. proxy passes request to WarpFilter with a request header which contains UUID
> 4. WarpFilter associates Inspection from the registry with given request
> 5. Warp proceeds with a request inspection
> 6. response is commited and sent back to the proxy (with given UUID as response header)
> 7. proxy catches the response and obtains ResponsePayload (with Inspection result) from the WarpFilter (using UUID)
> 8. proxy processes the ResponsePayload and passes the request to the client
> 9. the client processes response
> This would avoid a need for piggy-backing on request/response, so it will also eliminate need for response-wrapping (NonWritingResponse).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira