[
https://issues.apache.org/jira/browse/HAMA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015156#comment-13015156
]
Thomas Jungblut edited comment on HAMA-362 at 4/3/11 3:12 PM:
--------------------------------------------------------------
Played a little, hope you'll like this ;)
I made the getData and getTag methods in BSPMessage abstract and extended with
DoubleMessage (directly used in PiEstimator) and ByteMessage (quite the same
like the old Message). Added an empty Messagable Interface for that.
Please don't tell me that the communication uses the writable interface for the
serialization? In this case, I guess I have messed it up. :(
was (Author: thomas.jungblut):
Played a little, hope you'll like this ;)
I made the getData and getTag methods in BSPMessage abstract and extended with
DoubleMessage (directly used in PiEstimator) and ByteMessage (quite the same
like the old Message). Added an empty Messagable Interface for that.
> Design a new data structure for tag and message data of BSPMessage
> ------------------------------------------------------------------
>
> Key: HAMA-362
> URL: https://issues.apache.org/jira/browse/HAMA-362
> Project: Hama
> Issue Type: New Feature
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Fix For: 0.3.0
>
> Attachments: 362.patch
>
>
> The tag and message type are byte[]. However, I guess, the message of
> BSPMessage (almost) will be a {adjacent, vector, .., etc} *list*.
> By supporting generic datatypes, it will be able to represent any data
> structure and make easy-to-program.
> And, It should be compressible, writable, and flexible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
