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 <[email protected]> wrote: > WoW, I think we should not delete any data from physical DB. > > > On Thu, Oct 1, 2009 at 8:27 PM, Vassil Dichev <[email protected]> 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
