[JBoss JIRA] Closed: (NETTY-244) ReceiveBufferSizePredictorFactory

[Trustin Lee (JIRA)]

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

Trustin Lee closed NETTY-244.
-----------------------------

    Resolution: Done


ReceiveBufferSizePredictorFactory has been added as described above.

I did not deprecate get/setReceiveBufferSizePredictor() though because it is still useful when a user wants to switch the predictor dynamically.

> ReceiveBufferSizePredictorFactory
> ---------------------------------
>
>                 Key: NETTY-244
>                 URL: https://jira.jboss.org/jira/browse/NETTY-244
>             Project: Netty
>          Issue Type: Bug
>          Components: Core API
>            Reporter: Trustin Lee
>            Assignee: Trustin Lee
>             Fix For: 3.2.0.ALPHA1
>
>
> Configuring a ReceiveBufferSizePredictor using Bootstrap.setOption() is practically impossible because a stateful ReceiveBufferSizePredictor such as AdaptiveReceiveBufferSizePredictor must be instantiated for each channel.  Hence, we need ReceiveBufferSizePredictorFactory so that the transport implementations create a new predictor for each new channel.
> Implementation plan: Calling config.setReceiveBufferSizePredictorFactory() will instantiate a new ReceiveBufferSizePredictor immediately and call config.setReceiveBufferSizePredictor() with the new predictor if no predictor has been configured yet.  To avoid unnecessary instantiation of the default ReceiveBufferSizePredictor, it should be set to null by default and the default instance should be created in a lazy manner.  Deprecate get/setReceiveBufferSizePredictor() and store predictor instances in the 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira