I have a question about the board over use issue: How come we users don't have any problem, and we just find out later when we're using too many connections or whatever? Is there a way to put the breaks on the board or something? I mean, I'd rather not be able to connect for five minutes rather than end up getting booted from fangeek or whatever. Am I making any sense? I only have a vague idea what I'm trying to say.
I know we think we're OK for now, but assuming we have bumps in usage in the future....
Jesse, we (the coders) have no way to tell how many connections we're using at any given time, so we can't take the board down for a breather, or anything.
Lame. Not you, the system. If we only "have" 30 connections, they should stop us from using 80! Ah well.
If we only "have" 30 connections, they should stop us from using 80!
I dunno. I think it would suck for you guys if we suspended you every time you went over 50.
Any word on how we're doing this week, ma'am?
I think it would suck for you guys if we suspended you every time you went over 50.
I don't think suspended is what Jesse was thinking of. It wasn't what I was, anyway -- since we can and have been suspended for overuse. But if *our* code could check the connection level and just tell some people to wait, or something. Well, there'd be a riot, but you get the drift.
The problem with putting people in a queue to be connected is that people at the back would just keep hitting "Read New" (or hitting "Refresh" or whatever) because their computer would be unresponsive. I think it would ultimately create more connections, and make everything reeeeeeeeeeeeeeally slow.
think it would ultimately create more connections, and make everything reeeeeeeeeeeeeeally slow.
Not if checking redirected one to a "too busy" page without using any connections at all.
No, I don't like the thought of doing that -- I'd rather rein the code in. But I get the point.
Yeah, that's what I meant. If the person trying to make the 31st connection just had to wait until one freed up or something. I dunno.
What would be better would just be to delay page requests until one of the 30 connections was free. But that's not something we can easily implement.
I don't think suspended is what Jesse was thinking of.
Okay. When Jesse said "the system" it sounded like she was looking for something on the server side that prevented users from going over. The only server side option is to suspend you. I mean, maybe you could code something that tracked how many users were logging on and posting and cut excess posters off but it sounds like something that would involve a lot of work. I'm not even sure it would be that effective.
