A content engine can cache files transfered via ftp but not https [as the content is encrypted].
It can cache whatever file, including video, audio, ...
Content routing, content switching are just names.
They refer to how the traffic will be intercepted and forwarded to the content engine.
You could simply use a proxy solution and have your users setup their browser to use the content engine as a proxy, or you could transparently intercept http/ftp traffic via a router running wccp, or you could use a Layer7 device like a CSS to intercept the traffic and redirect to the content engine.
Regards,
Gilles.
