You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (Assigned) (JIRA)" <ji...@apache.org> on 2011/11/06 10:20:51 UTC

[jira] [Assigned] (HAMA-461) Extract a Message Service from BSPPeer

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

Thomas Jungblut reassigned HAMA-461:
------------------------------------

    Assignee: Thomas Jungblut
    
> Extract a Message Service from BSPPeer
> --------------------------------------
>
>                 Key: HAMA-461
>                 URL: https://issues.apache.org/jira/browse/HAMA-461
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>             Fix For: 0.4.0
>
>
> There's a problem, that we have more synchronized Collections than we need. localQueueForNextIteration (or similar name) is the only one which needs to be thread safe. At least only the put method could be synchronized, because reads does not need to be threadsafe.
> So we should refactor our messaging system from the peer itself. 
> A hint in architecture could give us HAMA-457.
> We have to add a factory which let's the user choice their protocol.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira