Enterprise IT
Multicast's Coming! It's Really Coming!
Given the constant drone of Internet and Web media saturation that jams the airwaves these days, I can hardly blame you for being somewhat jaded. Consequently, I cannot blame you for ignoring most of the stuff either. After all, once the network infrastructure is built and a traffic-flow pattern is more or less established, the network architect's job is to keep the network running. Despite evidence to the contrary (the number of hours a week you're working), this job has gotten somewhat easier. The positive effect of standards and mass adoption of IP has been that applications come and go without constant intervention by network architects. From the architectural point of view, this is as the network gods intended it to be: As long as you obey the rules and conventions established for this network, you can put up any server or application you like.
ReadGetting Philosophical About Supporting Users
In the Middle Ages, monks sat around and debated topics like how many angels could dance on the head of a pin and whether or not Adam had a navel. These may seem like ludicrous issues today, but for those who took religion seriously in the Middle Ages, no philosophical question was left unaddressed. One of the perennial debates for network managers today is how much support staff is required to support a user. These present day techno-monks who pray at the altar of technology have replaced discussions on the nature of the divine with discussions on the salvation of the dollar.
Read