[ 
https://issues.apache.org/jira/browse/DIRMINA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Trustin Lee resolved DIRMINA-439.
---------------------------------

    Resolution: Fixed
      Assignee: Trustin Lee

The following classes have been added:
* DemuxingProtocolEncoder
* DemuxingProtocolDecoder

Additional backward-incompatible changes:
* DemuxingProtocolCodecFactory has been written from scratch to reuse 
DemuxingProtocolEncoder and DemuxingProtocolDecoder.
* register() methods have been renamed into addMessageEncoder() and 
addMessageDecoder()
* disposeCodecResources() has been removed because you can always override 
DemuxingProtocolEncoder.dispose() and DemuxingProtocolDecoder.dispose().
* MessageEncoder.getMessageTypes() has been removed.  It was pointless and a 
pain for users.  Now the messageType is manually specified as a parameter of 
addMessageEncoder().

And... I updated JavaDoc a little bit so people can understand how the decoding 
works.



> DemuxingProtocolEncoder and DemuxingProtocolDecoder by refactoring 
> DemuxingProtocolCodecFactory
> -----------------------------------------------------------------------------------------------
>
>                 Key: DIRMINA-439
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-439
>             Project: MINA
>          Issue Type: New Feature
>          Components: Filter
>            Reporter: Trustin Lee
>            Assignee: Trustin Lee
>            Priority: Minor
>             Fix For: 2.0.0-M1
>
>
> DemuxingProtocolCodecFactory is somewhat monolithic and needs polishing.  It 
> would be more elegant to provide DemuxingProtocolEncoder and 
> DemuxingProtocolDecoder separately, and to implement 
> DemuxingProtocolCodecFactory by combining the two.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to