Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of benewu@gmail.com designates
 209.85.211.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=OoVVJ60IKdc4XTWyqMDLbWirC1irwniHoBY5RqjEeaUlh63+EHxsIcX58uUgMuKFC8
         lmqzV3otG0I6QEwoiEQD/TSU/tsGDWhEqg2zrck4Jbq4tEK82AlNMBj3s3/yQmL2BU0Q
         wHTP9msYmEW3FnANHzadjGB3LEbFAu2bQqwng=
MIME-Version: 1.0
In-Reply-To: <4db64d890910010530h4377ce8eq698597fc8e48e483@mail.gmail.com>
References: <fa2d9f450909300000k1dfb07eerfadd4ed15f122ad2@mail.gmail.com>
	 <4db64d890910010037o15c7d7du785deb893852e15c@mail.gmail.com>
	 <c7fc82820910010058p1a3d3e9ejf6428104d5b5cb04@mail.gmail.com>
	 <4db64d890910010339m64f516d5p7c362f38c5a3f97f@mail.gmail.com>
	 <fa2d9f450910010354o519c1542wb83a4ce986eb50b8@mail.gmail.com>
	 <4db64d890910010425n7b3f6ae6nd0cc820e3167ba59@mail.gmail.com>
	 <fa2d9f450910010430k6dc2259fo5ddaeb6701f51479@mail.gmail.com>
	 <4db64d890910010443l22e94871xab078a7a7a73a960@mail.gmail.com>
	 <c7fc82820910010527w1be82d2fo47c28acf6541e7c3@mail.gmail.com>
	 <4db64d890910010530h4377ce8eq698597fc8e48e483@mail.gmail.com>
Date: Mon, 5 Oct 2009 13:47:02 +0800
Message-ID: <4db64d890910042247h18a3e807tca6683fd11e08475@mail.gmail.com>
Subject: Re: Deleting user from access pool
From: Xuefeng Wu <benewu@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e6d2716f9dd014047529a443

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

Although I do not like delete any data from DB, but consider performance, I
do it.
For I'm not family with ESME.
The things is not easy I image after I delete user from access pool.
1. After I delete user from access pool, the message is send to his/her
mailbox as before.
Is there any cache and I need refresh the cache after delete user from
pool?

2. After delete user from access pool, user can not his/her message which
already in mailbox before.
Will check access pool when access mailbox?

I'm trying to understand more about ESME, especially Action!


On Thu, Oct 1, 2009 at 8:30 PM, Xuefeng Wu <benewu@gmail.com> wrote:

> WoW, I think we should not delete any data from physical DB.
>
>
> On Thu, Oct 1, 2009 at 8:27 PM, Vassil Dichev <vdichev@apache.org> wrote:
>
>> > So we only need to add a new attribute validate at Privilege and modify
>> > Privilege.hasPermission.
>> >
>> >  def hasPermission(userId: Long, poolId: Long, permission:
>> > Permission.Value) = Privilege.find(
>> >    By(user, userId),
>> >    By(pool, poolId),
>> >    *By(validate, true)*
>> >  ).map(_.permission.is >= permission).getOrElse(false)
>> >
>> > It's done at server-side?
>>
>> ...or delete existing permissions for this user. This way we won't
>> also have to edit the find*Pools methods.
>>
>> When a user has no permission in a pool, of course messages will not
>> be sent to their inbox anymore.
>>
>
>
>
> --
> Global R&D Center,Shanghai China,Carestream Health, Inc.
> Tel:(86-21)3852 6101
>


-- 
Global R&D Center,Shanghai China,Carestream Health, Inc.
Tel:(86-21)3852 6101

--0016e6d2716f9dd014047529a443--