You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would probably keep a lastActivity (datetime) in the user that would be updated on each of its action.
An active (bool) sounds great.
And for the automatic deactivation, a CRON job is more suited IMO. (Maybe symfony has some helper for this ?)
A manual scan can of course also be implemented.
This event is dispatched after the response has been sent (after the execution of the handle() method). It’s useful to perform slow or complex tasks that don’t need to be completed to send the response (e.g. sending emails).
I like the idea of this post That add a isActiveNow() method to the user and only update the database after a given time (2minutes in the example). This make sense if the user is a LEFT CLIC KILLER !!
Strategy 2 seems sweet to me. What do you think @n-peugnet ???
account deactivation based on inactivity.
This sounds like a parameter in
userClass
:quantity of days before inactivity pruning ( 0 for immunity )
And of course, store in the
User
class thelastConnect (datetime)
andactive (bool)
datas.But how to implement this ? should it be :
I know that I can easily implement a mix of 2 and 3, but maybe you have a better idea @n-peugnet ?
The text was updated successfully, but these errors were encountered: