On first glance Google Cloud Print looks like nothing more than an Internet version of networking printing, a technology which has been around for a long time; so one is naturally a bit surprised that Epson could get something like this wrong, but then I dug a little deeper... https://developers.google.com/cloud-print/docs/devguide ...and the protocol involves HTTPS, OAuth, JSON, and XMPP(!), so rather more complex t…
Wonder why they decided to invent their own protocol? I've used IPP over the internet via an SSH tunnel, it's slow but it works.
- IPP requires unique drivers for each printer. Some mobile devices (Chromebooks and iOS, I believe) don't allow installing drivers.
- IPP requires that you're on the same LAN segment, or that you punch a hole through your router. That doesn't work very well when interacting with foreign printers, and punching a hole through a router is too complex for many home users.
- IPP is limited to HTTP Basic/Digest auth, which isn't user friendly or secure. The traffic's also unencrypted. (And SSH isn't user friendly enough for home users.)
(Disclaimer: I work for Google, but not on Cloud Print.)