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)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C96CDA.30F6EE17"
Subject: AW: AW: AW: Thoughts on building a business around ESME
Date: Fri, 2 Jan 2009 13:59:34 +0100
Message-ID: 
 <30DB6ACF50A0A3439F39EFEB1C52E166078F222B@nets13ja.ww300.siemens.net>
Thread-Topic: AW: AW: Thoughts on building a business around ESME
Thread-Index: Acls1WusV5m1+6iAR3un32UlLLPBcgABIoX2
References: 
 <cdbebedf0812241024w55644526u9ded28e4256ae994@mail.gmail.com><E46117E31B684664928CCD1145636134@MARCIASONY><384A40FC-EF39-4C04-8024-0DBE7CECB369@gmail.com><3aade1dd0812281731k318ba452mffa24680b353232f@mail.gmail.com><30DB6ACF50A0A3439F39EFEB1C52E166078F2225@nets13ja.ww300.siemens.net><3aade1dd0901012342m5305471aj94ec93b75a9e4685@mail.gmail.com><30DB6ACF50A0A3439F39EFEB1C52E166078F2226@nets13ja.ww300.siemens.net>
 <3aade1dd0901020138u3cd2eef2g57bcfc1aec7b9acf@mail.gmail.com>
 <30DB6ACF50A0A3439F39EFEB1C52E166078F2227@nets13ja.ww300.siemens.net>
 <495DFF9D.3080503@fortybeans.com>
 <30DB6ACF50A0A3439F39EFEB1C52E166078F2229@nets13ja.ww300.siemens.net>
 <495E07ED.4040408@fortybeans.com>
From: "Hirsch, Richard" <richard.hirsch@siemens.com>
To: <esme-dev@incubator.apache.org>
Cc: <marcia@marciaconner.com>, "Bill Fernandez" <bill@billfernandez.com>

------_=_NextPart_001_01C96CDA.30F6EE17
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Agreed. I saw your comments on the lift mailing list. Looks like it is a =
good start but I didn't see any details on container-based auth.

D.=20


-----Urspr=FCngliche Nachricht-----
Von: Darren Hague [mailto:dhague@fortybeans.com]
Gesendet: Fr 1/2/2009 13:26
An: esme-dev@incubator.apache.org
Cc: marcia@marciaconner.com; Bill Fernandez
Betreff: Re: AW: AW: Thoughts on building a business around ESME
=20
Agreed. Top of my list right now is replacing/augmenting the OpenID=20
authentication with J2EE-based authentication (which would then allow=20
easy integration of directory servers, etc.), as a first step towards=20
implementing further authorisation options.

- Darren

Hirsch, Richard wrote:
>> Along with this, of course, we need to implement the =
personal/group/local/global permissions model.
>>    =20
>
> If you look at Mike's blog, you will see that he also thinks this sort =
of access control is critical. I agree and I think it should be on the =
top of our feature list.
>
> D.=20
>
>
> -----Urspr=FCngliche Nachricht-----
> Von: Darren Hague [mailto:dhague@fortybeans.com]
> Gesendet: Fr 1/2/2009 12:50
> An: esme-dev@incubator.apache.org
> Cc: marcia@marciaconner.com; Bill Fernandez
> Betreff: Re: AW: Thoughts on building a business around ESME
> =20
> I think that a useful lever for ESME adoption would be to make sure =
that=20
> Twitter (& Yammer?) integration is built-in - in other words, ESME=20
> should be usable as a Twitter client, so people can access their wider =

> network. Once this is under way, integrating local users becomes =
easier.
>
> A useful default would be for users to specify their Twitter ID on=20
> registration/first login, and this would be their ESME ID too - @xyz=20
> would then work seamlessly. We would then need a convention for=20
> specifiying local-only users (i.e. those who do not have a Twitter=20
> account) - perhaps @_abcd or something similar.
>
> Along with this, of course, we need to implement the=20
> personal/group/local/global permissions model.
>
> - Darren
>
>
>  =20


------_=_NextPart_001_01C96CDA.30F6EE17--