said by RH_User :TP-LINK is stating that they can't differentiate between video and game streaming while other manufactures are making those their key selling points.
I call marketing horses**t on this personally, or a lie by omission.
"video" is a pretty loose definition, the question for the actual device doing the QOS is HOW to identify "video."
At the enterprise level, which is where I work professionally, there's some pretty welldefined multimedia protocols
like RTP, RTSP, etc., but the TPLINK likely doesn't have a clue about what this is.
Secondly, what is the video source? Youtube? Netflix? A little embedded flash video? Again, the device has to have
the brains to figure out this is video and needs to be prioritize according. The example I posted above is one way
-- by destination IP address -- but to look up every IP address Youtube, et al. is or ever could be will drive you
bonkers. Imagine a neverending game of whackamole... to ID every IP address Youtube, or server(s) that host Youtube content, sits on.
Thirdly is how the video is being delivered... example via wellknown multimedia protocols or plain old HTTP. If HTTP,
then the problem you can run into is one video over HTTP stream can overload you, but the device isn't at fault,
it's just allocating the bandwidth according to the rules you configured.
On the other hand, games are generally alittle more well behaved, so ID'ing them by TCP or UDP port #
is pretty doable for a dinky little home idiot box.
tl;dr -- it comes down to what control you want at a level of technical knowhow you're comfortable with. Before you
buy into the marketing hype on the box, I'd do alittle research into the actual product.
My 00000010bits
Regards