But now, many vendors are starting to support a relatively new protocol that offers perhaps the best of both worlds: the Web Cache Communication Protocol (WCCP), which is sometimes referred to as Web Cache Coordination Protocol and other times as Web Cache Control Protocol. Whatever it stands for, WCCP isn't a routing protocol in the traditional sense, but it may be directing traffic around your network in the future, so you should familiarize yourself with its operation and benefits soon.
Requires Free Membership to View
|
||||
So, if you're thinking you need a cache or proxy, the WCCP model is definitely something you should consider, but because it's a little different, here are some things to think about:
- All traffic from clients to PCs doesn't go directly between the cache and the client, but flows several times through the router, which means you may need more muscle. Don't skimp on processing and memory for WCCP-enabled routers. And pay attention to traffic flow so you don't create bottlenecks.
- You'll need to prepare your helpdesk or network operations support people to troubleshoot a somewhat more complex environment.
- Much like VOIP is causing organizational changes between voice and data IT departments, a lot of new technology like WCCP will be blurring the delineation of responsibilities between the server and application and network support teams. Sort this out before your first outage.
This was first published in December 2005
Network Management Strategies for the CIO

Join the conversationComment
Share
Comments
Results
Contribute to the conversation