Hi All,
It seems there is room to improve the current CarbonMessage implementation.
Following are few main areas where we can improve its functionality.
- At the moment there are too many ways to get the message body from the
CarbonMessage
- getMessageBody()
- getInputStream() - This is a http specific impl.
- getMessageDateSource()
- There are too many types of CarbonMessages in carbon-messaging that
are only used by a specific transport implementation
- BinaryCarbonMessage
- ControlCarbonMessage
- DefaultCarbonMessage
- MapCarbonMessage
- SerializableCarbonMessage
- StatusCarbonMessage
- StreamingCarbonMessage
- TextCarbonMessage
- Most of above CarbonMessages do not adhere to the contract that is
imposed by the CarbonMessage interface.
Considering these facts, I believe we should refactor CarbonMessage before
others starting using it in their implementations. Please let us know your
thoughts as well :)
--
Regards,
*Shafreen*
Software Engineer
WSO2 Inc
Mobile : 077-556-395-1
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
