[
https://jira.jboss.org/jira/browse/JBMESSAGING-1394?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1394:
--------------------------------------
This task and 1438 need to be done together.
We should change our MessagingBuffer abstraction to be very similar to netty ChannelBuffer
then we can avoid the complex conversion layer.
We then always use heap buffers not dynamic buffers when encoding packets.
We should also take the code for DynamicChannelBuffer squash the hierarch and copy into
JBm project as a generic resizable buffer, this is used in the message at creation.
Refactor messaging buffer interface for netty integration
---------------------------------------------------------
Key: JBMESSAGING-1394
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1394
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0 Beta
MessagingBuffer needs to be refactored to work more like netty3 - i.e. no limit() or
flip()
--
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