[
https://issues.apache.org/jira/browse/DEFT-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070072#comment-13070072
]
Johnathan Meehan commented on DEFT-142:
---------------------------------------
With an initial implementation in line with this:
Original
- 14480.65 [#/sec] (mean)
- 15229.27 [#/sec] (mean)
- 14367.18 [#/sec] (mean)
- 14283.03 [#/sec] (mean)
Reflection
- 7405.82 [#/sec] (mean)
- 7487.22 [#/sec] (mean)
- 7449.57 [#/sec] (mean)
- 7464.47 [#/sec] (mean)
Oh, dear. Given the nature of the object, would we perhaps consider clone?
Cloned
- 14947.91 [#/sec] (mean)
- 16111.44 [#/sec] (mean)
- 14321.85 [#/sec] (mean)
- 14236.77 [#/sec] (mean)
- 14437.61 [#/sec] (mean)
> Dynamic creation of RequestHandlers
> -----------------------------------
>
> Key: DEFT-142
> URL: https://issues.apache.org/jira/browse/DEFT-142
> Project: Deft
> Issue Type: New Feature
> Assignee: Johnathan Meehan
>
> The outcome after a discussion with github.com/inferno-:
> (In the current design) it's volatile to have fields in user defined
> RequestHandlers in conjunction with asynchronous calls. (intermediate request
> (to same RH) could change the state of the RH)
> We should investigate the performance impact for dynamic creation of RH.
> Proposed solution:
> 1, Map<String, RequestHandler> => Map<String, Class<RequestHandler>>
> 2, Application.getHandler should create the appropriate RequestHandler using
> reflection.
> 3, UT / benchmark
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
