Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of
 thomas.jungblut@googlemail.com designates 209.85.220.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=B462XfB+NL6a1f9nvaUGP3CWBfocT37imjQHbGjoDDvAnDvvT3RCexWg9I4rEITQoQ
         Ryo7wHiraNlu/t3bvIIiHy2QG2kXLOss1406+gGCyxTIxGjcdA7qtbG/CSqVIExQS+Kv
         G0R2reDxus1zYuuq0pETWwr4N37mN9doVmkN8=
MIME-Version: 1.0
Date: Sat, 11 Jun 2011 09:45:07 +0200
Message-ID: <BANLkTikZjpOZMW7QRA9ZasxyGLmcy4tUbg@mail.gmail.com>
Subject: Package Layout & Message class conventions
From: Thomas Jungblut <thomas.jungblut@googlemail.com>
To: hama-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec501667177ae7504a56addb3

--bcaec501667177ae7504a56addb3
Content-Type: text/plain; charset=ISO-8859-1

Hey all,

I think we can improve our package layout to clean up the BSP package.
For example we could put the Message model classes and the task related
classes into their own package.

And I would like to state some conventions on the message classes.
So for example we have a primitive like a boolean, the message would be
called BooleanMessage. So the data part is a boolean and the tag is a
string.
If we are changing the tag to a non-string class we are using a combined
name like IntegerDoubleMessage. So the tag part is an integer, the data part
is a double.

What do you think?


-- 
Thomas Jungblut
Berlin

mobile: 0170-3081070

business: thomas.jungblut@testberichte.de
private: thomas.jungblut@gmail.com

--bcaec501667177ae7504a56addb3--