The IS public webserver did get creamed. They just had its .conf file set to only allow a *very* finite number of connections.
The server itself was doing just fine ... CPU utilization, I'm told, was around 4 percent even at the peak.
The .conf settings, which were at Apache's default values, were changed to allow many more connections.
We've been working separately with Business and Finance on an emergency notification system that would closely mirror what you suggest, as long as we can do it without too much network overhead.
Robert J Crisler
Manager, Internet and Interactive Media
321 Canfield Administration Building
University of Nebraska-Lincoln