1. For normal HTTP, I'm pretty sure our server can handle it. Our uplink is probably our limiting factor. 2. The CEC won't care. 3. d00d, if you're going to slashdot my box, why don't you at least use a link to do it?
Do you really *need* to upgrade those 400Mhz machines? Look at your user's needs; could you be better served by looking at a thin client solution, with either a Linux/X11 or Win2K/Terminal Server config? Consider: you get better managability, since all the apps are on the server. The people who have extra power now don't have it going unused, it's reallocated to those who need it more. Furthermore, (especially with an all-*NIX solution) the liscencing costs are far less.
Slashdot Mirror
1. For normal HTTP, I'm pretty sure our server can handle it. Our uplink is probably our limiting factor.
2. The CEC won't care.
3. d00d, if you're going to slashdot my box, why don't you at least use a link to do it?
Nope, it toasted my locations too :-(
Do you really *need* to upgrade those 400Mhz machines? Look at your user's needs; could you be better served by looking at a thin client solution, with either a Linux/X11 or Win2K/Terminal Server config? Consider: you get better managability, since all the apps are on the server. The people who have extra power now don't have it going unused, it's reallocated to those who need it more. Furthermore, (especially with an all-*NIX solution) the liscencing costs are far less.
Hmmm...
About a year ago (I think) I found on AOL's site a Java-based AIM for Linux. It was a tarball with the JRE and the AIM client in one.
It dissapeared shortly thereafter, but oh well... gaim worked too...