No, my definition of "thin client" isn't different from that of the rest
of the industry, considering the company I work for, Neoware, basically is
the rest of the industry. We're the leading Thin Client provider in the
world next to Wyse Technologies, but anyone who knows the industry
intimately knows that Wyse is approaching its last days (we almost bought
them out last quarter). That said, look at the units offered at
www.neoware.com if you're curious. My group develops the Linux version of
our products. I used to work on the WinCE and XPe versions as well but
NeoLinux (the custom Linux distro we use on our Thin Clients) is much more
fun to engineer.
Anyway... "Any chip that can't render fast enough to function in a thin
client is broken." - True, but I didn't say the chipsets didn't render
fast enough to function. They all function. However, when the CPU of the
TC is not the bottleneck, apparent differences can be seen (in 2D graphics
benchmarks) between the various graphics chipsets. Either way though
"rendering fast enough" is completely relative.
A specific example would be to compare two hypothetical hardware platforms
both running 800mhz VIA C3 processors, one unit using a VIA graphics
chipset, the other using an S3 chipset. In an ICA or RDP benchmark the
800mhz unit with the VIA chipset would complete a sequence of 2D X drawing
directives 30% faster than the S3 chipset. There ya have it.