Load limit for CCBill member area logins?
 

I have a project I'm working on that will require a lot of people logging in many times per day to one members area regulated by CCBill authentication (.htaccess).

1. At what load level should I start worrying about curruption of the .htaccess file... in other words, if TOO many people are logging in TOO many times a day, -EDIT - AND people are signing up to the site at the same time (meaning the .htpasswd file is in a constant state of read\write flux), -END EDIT - is there a point where things may break down?

And if so...

2. I am considering having a mySQL db handle the user authentication instead of the above scheme, but it would have to be based on the information from CCBill regarding usernames, passwords, expirations, etc.

Does anyone have experience with that? Any recommendations as to how to go about syncing CCBills stuff with my own mySQL database?

Thanks.

are you completely sure you know what your talking about?

How about limit how many times someone can shoot a load in a single day

Yes.

Let's say a ton of people are logging in at one time to my members area. At the same time, other people are signing up to the site. That means CCBill's script will be writing to the .htpasswd file at the same times as it is being accessed by many users. I probably should have clarified the constant simultaneous read\write aspect in my post. :1orglaugh

I'm just curious if the fact that it will be read and write accessed so many times so frequently will cause any trouble.

It's just something I'm playing, so I'm curious. :)

Well I write all users and pass to a SQL DB, do that too and then write a program that checks if user a is logged in etc.

ccbill has a modified version of the ccbill-local.cgi that works with MySQL . . .

use mod_auth_mysql if you are using a MySQL DB. we do >2,000 password auths a sec, no problem. (it auths every file in the protected dir)

I know (at least one) big program uses .htpasswd files and does fine. don't worry.

Thanks guys. :thumbsup