|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
18/Oct/05 01:37 AM
|
|
There's no way to release resources allocated in the constructor for ProtocolEncoder and ProtocolDecoder. It becomes a problem when user implements them to acquire resources that must be released explicitly such as file descriptors.
We could simply add dispose() or release() method to give a change for user to release them when the connection is closed, but it becomes a big problem when user shares an encoder or decoder instance for multiple sessions. And we also have to consider stateless transport types such as datagram carefully.
|
|
Description
|
There's no way to release resources allocated in the constructor for ProtocolEncoder and ProtocolDecoder. It becomes a problem when user implements them to acquire resources that must be released explicitly such as file descriptors.
We could simply add dispose() or release() method to give a change for user to release them when the connection is closed, but it becomes a big problem when user shares an encoder or decoder instance for multiple sessions. And we also have to consider stateless transport types such as datagram carefully. |
Show » |
|
Improvement
Closed
Minor
Provide a way to release resources for ProtocolEncoder and ProtocolDecoder
