[
https://issues.apache.org/jira/browse/DEFT-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072774#comment-13072774
]
Johnathan Meehan commented on DEFT-142:
---------------------------------------
Anybody mind taking a quick look at "deft-142_clone.patch"? Looking at it now I
am wondering if it is along the right lines... perhaps I missed something.
Assuming this is a decent start I was thinking that we could bring this change
to a single method, getHandler(HttpRequest), where we provide the functionality
to modifiy "internal" handlers such as "BadRequestHandler". Struck me that
people might well want to provide customised handlers for some of the requests
and now could be an opportune time to provide that facility.
> 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
> Attachments: deft-142_clone.patch, deft_142_reflection.patch
>
>
> 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
