[ 
https://issues.apache.org/jira/browse/HTTPCORE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322495#comment-16322495
 ] 

ASF subversion and git services commented on HTTPCORE-507:
----------------------------------------------------------

Commit c7feb5400865c84661eddf16e499af9ec97d70b6 in httpcomponents-core's branch 
refs/heads/4.4.x from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=httpcomponents-core.git;h=c7feb54 ]

[HTTPCORE-507] Add generics to DefaultHttpServerIODispatch to specify
the NHttpServerEventHandler implementation type.

> Add generics to DefaultHttpServerIODispatch to specify the 
> NHttpServerEventHandler implementation type.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCORE-507
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-507
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>            Reporter: Gary Gregory
>            Assignee: Gary Gregory
>             Fix For: 4.4.9
>
>
> Add generics to {{DefaultHttpServerIODispatch}} to specify the 
> {{NHttpServerEventHandler}} implementation type.
> Change:
> {code:java}
> public class DefaultHttpServerIODispatch
>                     extends AbstractIODispatch<DefaultNHttpServerConnection>
> {code}
> to use generics in order to type the handler like this:
> {code:java}
> public class DefaultHttpServerIODispatch<H extends NHttpServerEventHandler>
>                     extends AbstractIODispatch<DefaultNHttpServerConnection>
> {code}
> This allows call sites to call getHandler() and get the exact type that was 
> passed in on construction instead of getting back the interface and going a 
> type-cast (if you need access to the actual class.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to