Architecture question using deferred tasks

Question

Hi ,
I have a requirement where I need to expire the accounts based on their inactivity for a period of time.
But this period should be reset if there is any unlock or reset password operations for this user.
Is it a good practice to add a deferred task for achieving this?
I understand that I need to scan for any differed tasks instances of expiring accounts and remove them as part of the reset process. Does this sound reasonable?
Any one have successfully implemented this kind of feature? Is there a better way to do this?
Your help is highly appreciated.
Thank you,
Ani.

Answer 1

Hi,
One way which I can suggest as deferred task seems little complicated :
1. Add an extended attribute for user say.. LastUpdatedDate, make is searchable.
2. Update this attribute on any kind of user update.
3. Now put a deferred task which will search for user with the above attribute value as say[ current date - x (where x is the inactivity days)] and do what ever you want to do with the returned list of user.
This way no check nothing and even 'x' is configurable with the help of a rule or something.
Hope this will help you.
Regards,
Surinder
Edited by: Surinder_Singh_Bora on Mar 31, 2008 3:40 PM