Comment Re:huh? (Score 1) 70
Imagine that you have 4000 branches all around the world. And imagine that the average latency across these links range from 10ms when its close, to over 400ms when its far. If you've ever tried to load a website with 30+ images/javascript/css with IE's measly 2 http simultaneous connections. ONLY then, will you realize how necessary this is. Because its either WAN optimization (more for latency reduction...not so much for bandwidth reduction), or local servers in 4000 branches.
Now throw in a little CIFS acceleration (ms exchange, or file sharing), or a little http caching, and you have a USD$2500 device that's worth its weight in gold. Namely due to reduction in local servers/backups, and a huge reduction in customer *slowness* complaints. Unfortunately, when your primary business is not application development, you have very little choice among which applications you can run across your WAN.
Now throw in a little CIFS acceleration (ms exchange, or file sharing), or a little http caching, and you have a USD$2500 device that's worth its weight in gold. Namely due to reduction in local servers/backups, and a huge reduction in customer *slowness* complaints. Unfortunately, when your primary business is not application development, you have very little choice among which applications you can run across your WAN.
