Buddyauth feature request (max sessions fix)

[mylo]

Hi,

I'm experiencing a problem which I guess a lot of people will find when using a relogger, whenever DB crashes and is relogged there is a period of a few minutes where it sits there spamming trying to login, which fails as it is at max sessions.

This is bad for the user as it's causing the relogger to fail sometimes, and also spamming your servers with login attempts.

There are a few solutions, either for a new session from the same IP to automatically kill the session that contacted the server longest ago (this should be the crashed DB I guess if active sessions are constantly talking to db server), or for a user definable time-out that can be set very short to say 5 seconds, so that sessions would time out much quicker and the relogger wouldn't fail.

This would reduce server load and authentication request spam for you as well as not being so frustrating for users when DB crashes.

Thanks

 

[Tony]

its not a bug or something,its how the auth system works

 

[mylo]

I explained the situation clearly with a cause and possible solutions, I think if a user has bought 3 sessions but cannot use them due to a DB crash then it is a bug personally, it has to be either a bug or a "feature"...

 

[Tony]

there is nothing we can do about it


the relogger authors should find a way to deal with it,adding a delay or something