Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <49B97A45.8020504@fortybeans.com>
Date: Thu, 12 Mar 2009 21:10:29 +0000
From: Darren Hague <dhague@fortybeans.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: esme-dev@incubator.apache.org
Subject: ESME Groups
References: 
 <30DB6ACF50A0A3439F39EFEB1C52E166078F233F@nets13ja.ww300.siemens.net>
 <cdbebedf0903011331i3eb9d8d0na3bf48028aec6677@mail.gmail.com>
 <65C94484-A8D1-4AD5-B2A9-B6356E22755C@gmail.com>
In-Reply-To: <65C94484-A8D1-4AD5-B2A9-B6356E22755C@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The results of David and my pub-based design session are now in the 
Apache ESME wiki:
http://cwiki.apache.org/confluence/display/ESME/ESME+Groups

Yes, this is just a photo of a notebook page right now. I will decrypt 
this and update the wiki, but we were basically riffing on how to 
implement the group/pool ideas we all thrashed out here on the list a 
few weeks ago, in combination with a security model which will not 
cripple system performance (not a trivial idea).

Step 1, I think, will be to implement a Security Manager concept which 
can be applied to the reading/writing of messages. Following on from 
this, we can build the internals of the Security Manager implementation 
- this will utilise the group concept. In parallel, it would be good if 
the UI guys can start thinking about how users would create/edit 
groups.  As an initial idea for actually sending the messages, simple 
Twitter-like d- and @-syntax can be used to refer to groups as well as 
users.

Thoughts, anyone?

Cheers,
Darren