Got 503.htm a few times this morning, with "sorry, but the Ranch is quite busy right now. Please try again in a few minutes." I was thinking of distributed computing as a solution, -- after all, the more people use the service, the more computing resources become available, so the problem seems to take care of itself. I got to think it through.
We're sort of doing distributed computing now. We blew out Apache a couple of years ago. So now we have about six servers. That is, we have have six servers running on one box. Our plan is to get another box and move the biggest server to that box.
We're sort of doing distributed computing now. Paul, actually what I meant was to compute on the client side, rather than on the server side. That way, no servers need to be added no matter how many users there are.
A peer-to-peer BBS? Has anybody ever implemented anything like this? I suppose you could say that's what Usenet is, but that's rather an altogether different model. Interesting concept, but in any event, not practical AFAIK.