Slashdot Mirror


Google Drafts Cloud Printing Plan For Chrome OS

snydeq writes "Google is unveiling early-stage designs, software code, and documentation for a project whose goal is to let users of the company's Chrome OS print documents to any printer from any application. Called Google Cloud Print, the technology would dispense with the need to install printer drivers by routing print jobs from Web, desktop, and mobile applications via a Chrome OS Web-hosted broker. 'Rather than rely on the local operating system — or drivers — to print, apps can use Google Cloud Print to submit and manage print jobs. Google Cloud Print will then be responsible for sending the print job to the appropriate printer with the particular options the user selected, and returning the job status to the app.'"

30 of 126 comments (clear)

  1. So Google invented.... by Maniacal · · Score: 5, Funny

    So Google invented a print server. Brilliant!!! Those guys are AMAZING. What will they do next. :P

    --
    MG
    1. Re:So Google invented.... by WrongSizeGlass · · Score: 2, Insightful

      So Google invented a print server.

      Indeed they did ...

      What they need to do is not send print jobs to the cloud just so they can come back "down to earth". Get together with the major printer manufactures, develop a common intermediate print-job description language and print all ChromiumOS jobs in that PDL. The manufactures can implement their own drivers in the firmware of their printers. This gives us true plug & play, eliminates the need of installing drivers and lets everyone print on any printer they encounter that supports this technology.

      It goes without saying that this should be open source and available on all other platforms as well.

    2. Re:So Google invented.... by Jazz-Masta · · Score: 3, Funny

      Ah yes, why print locally when you can send it to Google and have them send it back to you. Instead of a print driver...those nasty inefficient things (no really, anyone use HP drivers?), we'll install some software, send it to...THE CLOUD!!!...and have it sent back to us to print.

      And, in the meantime, if someone or something happens to "grab" that confidential document you are trying to print, no problem. What's that? government documents you are trying to print? Send 'em to the cloud, China can't get them there...oh wait.

    3. Re:So Google invented.... by 0racle · · Score: 4, Insightful

      You mean something like Postscript?

      --
      "I use a Mac because I'm just better than you are."
    4. Re:So Google invented.... by WrongSizeGlass · · Score: 4, Funny

      You mean something like Postscript?

      I knew there was a word for it ;-)

    5. Re:So Google invented.... by binarylarry · · Score: 4, Funny

      How are they going to insert ads into your printed documents if you're not sending them to cloud?

      --
      Mod me down, my New Earth Global Warmingist friends!
    6. Re:So Google invented.... by 0100010001010011 · · Score: 2, Interesting

      Zero conf is the solution. Nearly every networkable printer these days has it.

      I remember when I first got OS X and walked into a random computer lab, I instantly had all the printers available. Truly zeroconf.

      Now my entire home network is zeroconf configured (oxymoron?). I stopped giving devices static IPs. The sheeva plug is plug.local, the mac is mac.local, open solaris is server.local.

      ZeroConf+Postscript should be able to print to anything for sale today.

    7. Re:So Google invented.... by Graff · · Score: 2, Informative

      It seems like what they have re-invented is the Common Unix Printing System (CUPS). Like the new Google Cloud Print, CUPS encapsulates the drivers for printers, filters and converts jobs based on the type of printing needed, sets classes of printers where the first available will be used, and much more. You can read a summary of some of the top features at its Wikipedia page.

      It's also open-source, licensed under the GPL and LGPL, and has been used in Gnome, KDE, Mac OS X, and several Linux variants for years.

    8. Re:So Google invented.... by Daengbo · · Score: 2, Interesting

      Printing sucks. Always has, always will. Just don't do it.

      It's for this reason that I was a little disappointed about GDocs new "more paper-like" interface. I always figured people would do 95% of the work collaboratively and without real interest in formatting, and have on guy download and do final formatting only if the product needed it.

      It seems that this new interface is going to encourage more time-wasting formatting debates and more useless printing.

    9. Re:So Google invented.... by fuzzyfuzzyfungus · · Score: 2, Informative

      While zerconf is nice(and seems to have been made more broadly useful than uPNP, which largely confines itself to reconfiguring NAT routers at the behest of bittorrent clients), it doesn't really match Google's use case all that well. Consider a few points:

      Authentication: zeroconfing stuff works fine in a trusted home environment, or in an .edu lab where they are resigned to rolling the print costs into student fees(or, incidentally, it is totally possible that their crack team of MCSEs connected the printer to the printserver, and locked down the printserver permissions, and then walked away, leaving zeroconf and IPP wide open. Back in the day, that was what usually happened to the various workhorse HPs you'd see in uni labs. They'd be connected to some proprietary print billing system, that either took coins or integrated with student accounts; but FTP and telnet would be wide open, and you could dump jobs to them that way). In any case, zeroconf makes it easy to find stuff; but it only makes access easy if you adopt a totally naive "trust all" model.

      The interwebs: Zeroconf, Apple's flavor at least, depends on multicast working properly and plays various DNS tricks. No big deal on a little LAN, not so much with the working across the internet, barring pretty major changes.

      In a number of cases, that just isn't good enough(though it is nice to have, when you are on your friendly LAN). If I am sitting offsite somewhere, having to establish a VPN connection to my home LAN to print something pretty much immediately rules out anybody who isn't a gearhead, or a corporate type with their laptop set up for them. If it doesn't work over the internet, it doesn't work(Google, of course, has the additional motivation that it'd be really handy for them to be able to send a print job, on your behalf, directly from Docs to your printer, without you having to download it. That is merely convenient on the desktop; but it is downright valuable if you are trying to work from some resource constrained phone or something). Or, with the proliferation of cellular connections, I might be sitting right next to the printer; but, logically speaking, be far, far away across the internet from it. Yeah, if I understand what I'm doing, I can switch over to LAN, and do my thing; but if reasonably simple technology can spare me the effort, all the better.

    10. Re:So Google invented.... by J'raxis · · Score: 2, Informative

      And, in the meantime, if someone or something happens to "grab" that confidential document you are trying to print, no problem. What's that? government documents you are trying to print? Send 'em to the cloud, China can't get them there...oh wait.

      Hear, hear. It never ceases to amaze me how virtually every new Google "service" further erodes people's concept of privacy. And people just eat it up. If someone ever wanted to intentionally socially engineer away the concept of "privacy" to begin with, this is how to do it. Makes you wonder...

    11. Re:So Google invented.... by iluvcapra · · Score: 4, Insightful

      Or more specifically one universal printer driver.

      Postscript? It doesn't control the paper handling, as you point out, but there are a lot of different solutions on offer along these lines. Xerox printer/copiers run a web server that allow you to upload print jobs through a web interface and set paper handling/stapling/job deferment/billing etc. through an HTML form. A generalization of this would be nice, but what's the difference between typing the IP address of the nearby printer to submit a job and typing http://print.google.com/ to submit a job, fundamentally?

      Printing sucks on Linux, Windows, Mac, and every other platform because it is a very large problem, and abstractions tend to hide controls that are necessary to produce decent results.

      I don't know what you're doing wrong or right, but CUPS is excellent.

      Also what should be done if an document overflows from the size of the printable area. (If you are printing things to go in a button machine, you want the image to not be scaled. If there is an important disclaimer at the end of the page you want the page scaled so the disclaimer shows.

      This is a client issue, not a printer issue. The printer should treat all information as semantically neutral, letting the client know what the page geometry is and making its own adjustments accordingly.

      Also brightness of the paper, and color of the paper are issues if you actually care about what the finished product looks like. Spot colors are another factor for the print driver to deal with.

      ColorSync. Again, the technology for all of this stuff has been around since the 80s. The only real difference here is Google is trying to commoditize it over the WAN, since making it easier to run is an important part of making Google app/Chrome TCO lower, demand higher, thus ad revenues higher.

      --
      Don't blame me, I voted for Baltar.
    12. Re:So Google invented.... by micheas · · Score: 3, Informative

      If you were to say that cups is the best solution we have today, I might agree with you, but posts like this one http://weblog.zamazal.org/cups-sucks.html are pretty common for cups, and printing is at least as bad on other platforms.

      The big problem with cups is the UI and the ablity to secure it so you can safely put your print server on the net, without random spammers printing their ads on your printer.

      Cups is a good start, but there is a long ways to go.

      Shouldn't you be able to print your report for the office from home or on the road on a laptop?

      Cups could get there, but right now it is a long ways from being easy.

    13. Re:So Google invented.... by Fastolfe · · Score: 3, Insightful

      Hear, hear. It never ceases to amaze me how virtually every new Google "service" further erodes people's concept of privacy. And people just eat it up. If someone ever wanted to intentionally socially engineer away the concept of "privacy" to begin with, this is how to do it. Makes you wonder...

      Presumably, every document being printed on Chrome OS already exists in "the cloud". What additional erosion of privacy is created by adding the ability to take those documents and send them to a printer? If you're using Google's cloud, they already have the data. If you're using someone else's "cloud", I think the idea is that they'd implement their own printing service. None of your data should be shuttled around the Internet promiscuously except to your printer. Am I missing something?

    14. Re:So Google invented.... by Fastolfe · · Score: 2, Insightful

      Your concerns have nothing to do with the Cloud Print service and everything to do with storing your data in the cloud. If you don't want to store your data in the cloud, neither Chrome OS nor the services associated with it are for you.

      For those that are OK adopting this model, your data already exists in the cloud, so adding the ability to send that data to a printer doesn't do anything to reduce your privacy.

  2. So, what is next? by smith6174 · · Score: 2, Interesting

    I didn't think of this one. Google now wants to see everything you print too? George Carlin was right when he said we would eventually trade all of our freedom in exchange for new toys.

  3. What will they do next. .... by butterflysrage · · Score: 4, Insightful

    make it work when the internet goes out?

    --
    the preceding post was not spell checked... suck it.
    1. Re:What will they do next. .... by severoon · · Score: 2, Interesting

      I think perhaps the main point if this is being missed.

      Does anyone remember Jini? It was the technology developed by Sun prior to EJBs that promised to make efficient distributed computing and pervasive connectivity a reality. Except, it never caught on because it required software development organizations to invert their staff profile. Instead of having a few device driver coders and enterprise architects, a few more low-level programmers and architect/designers, and the bulk of the staff in standard software development, Jini would have pushed the work to the outsides of that bell curve; nearly every developer would be playing the role of either device driver programmer or enterprise architect on most Jini projects. Recognizing this, Sun's compromise was EJBs, a distributed technology that brought half the functionality with perhaps 10x the weight.

      Now we see that Google has rolled out a series of technologies that can all be combined to accomplish a similar vision: Google App Engine (cloud development platform), Chrome browser (thin client presentation layer), Google Apps (useful software including Docs, sensitive data hosting such as Health, etc), Chrome OS / Android (netbook/device hardware layer), and Wave (real time connectivity platform and protocol--the *product* most people think of as Wave is one possible manifestation of a front end to the Wave back-end and GWFP, but largely irrelevant for the purposes of the point I'm making here).

      Laugh if you want, but demonstrating this bit about being able to host drivers in the cloud for any old device adds a necessary, though admittedly not particularly flashy, part of a fearsome distributed computing technology stack.

      --
      but have you considered the following argument: shut up.
  4. Wait... What? by Monkeedude1212 · · Score: 4, Funny

    let users of the company's Chrome OS print documents to any printer from any application.

    Lets see here...

    www.goatse.cx

    File -- Print -- Select Printer: CEOOFFICEPRINTER.Apple.Com

    Pages: 200

    PRINT

  5. Fine! by hyfe · · Score: 5, Insightful
    Fine, alot of you don't see the need for this. Don't use it, and more importantly, don't complain about it.

    I work as teacher, mostly for fun, and got suckered into supposedly being admin for the school network. In reality I'm a general janitor / IT-support though. I have next to no time to spend on actually setting infrastructure. If anybody gives me a simple solution for printing any document, from any operating system on any computer easily to our public printers I'd give them a big, wet kiss. I certainly don't know any easy way of doing it now, because adding printers to students laptops is a f***king bother, and there's always some weird problem.

    I'm certainly sure there's lots of other uses for this, aswell as lots of places it won't be usefull.

    --
    "" How about taking the safety labels off everything, and let the stupidity-problem solve itself? """
    1. Re:Fine! by vbraga · · Score: 2, Interesting

      Doesn't Bonjour solves your problem?

      --
      English is not my first language. Corrections and suggestions are welcome.
    2. Re:Fine! by jedidiah · · Score: 2, Insightful

      Someone mentioned "postscript" a while back.

      This is all you really need.

      Set a language standard for the printing and have the network & print queue sort it all out.

      All Google is doing is dressing up an ancient Unix idea and giving it a lot of unecessary added complexity.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  6. Re:first! by WrongSizeGlass · · Score: 2, Funny

    Why is this item red?

    Because Google will support color printing?

  7. Re:No. Hell No. by GIL_Dude · · Score: 2, Insightful

    Not just google sniffing the document. Having the government subpoena the document from Google (as it will be somewhere in their huge data store). Of course, my printer (and yours too) don't have an outward facing IP and we don't port forward our routers to it either for exactly the reason you mention. Spam, or just some jack nut deciding to waste all your paper and toner.

    I guess I would have more faith in it if it does the equivalent of creating the print file, sending that back to your Chrome device, then your chrome device does the equivalent of the old ability to just copy formatted print file to a printer. So nothing on your network gets exposed. But certainly there would need to be a very stringent policy on what Google could do with your print file and how long they could store it (0 seconds!).

  8. As long as your printer is exposed to the internet by ravenscar · · Score: 2, Insightful

    Sure it will allow you to print to any printer...that can be accessed via the internet. I'd wager that's a step a large number of people haven't taken when it comes to their home networks.

  9. alpha by jDeepbeep · · Score: 2, Funny

    I'm trying out the alpha, and the printer has an undecipherable message.

    PC_LOAD_GOOGLE

    What does that even mean?

    --
    Reply to That ||
  10. No local drivers for remote printers--good idea. by Seor+Jojoba · · Score: 4, Insightful

    I always thought it was a terrible design to require installation of hardware-specific drivers for a remote printer. You know how you get some crummy nonstandard print status window popping up when you print? Like it will be this hyperbranded thing with a zazzy, colorful diagram of your printer and "buy toner online now" button on it. Almost indistinguishable from a pop-up advertisement except that there is a progress bar showing your print job going through. As far as I can tell, that is the only reason for there to be local drivers for remote printers--so manufacturers can bring up their fancy nonstandard dialogs out of some paranoid necessity to convince you your printer is not a commodity item. In fact, they would probably prefer you called it something other than a "printer", i.e. your "HP-SmartPaperDuplicator TM".

    So, yes, this is one thing Google seems to be getting right--a standard print dialog with no local drivers for remote printers.

  11. Yes and No. by fuzzyfuzzyfungus · · Score: 2, Insightful

    Frankly, I have zero interest in sending my printed documents through Google's grubby hands. However, I think that their implementation shows real promise and(as is even mentioned in their documents) it would not be difficult for 3rd parties to run their own "cloud" print servers.

    Even for comparatively small organizations, being able to ditch the ghastly nuisance of driver-shuffling and the more-or-less-strictly-LAN-bound world of SMB printer sharing, for a system that will work on any device with internet access to the organization's print host and the ability to spit out a PDF would be great. Google's approach may or may not be the best approach to the reinvention of the print server; but it has strong potential to be good enough quite easily amenable to 3rd-party implementation, build largely on standardized components(HTTP, PDF, PPD, bit of XMPP, etc.) and Google's support might help it reach critical mass.

  12. Re:No. Hell No. by jimicus · · Score: 2, Interesting

    Of course, my printer (and yours too) don't have an outward facing IP and we don't port forward our routers to it either for exactly the reason you mention.

    This wouldn't necessarily pose a problem.

    Google for Domains customers can install a small app to go on a Linux server which communicates with them and allows you to integrate your systems with theirs. It gets around the firewall by the simple expedient of establishing the connection from the inside out. If you were to integrate that with Zeroconf - abracadabra! Any Google user can indeed print directly to all your printers.

    I wouldn't be too surprised to see something like that built into Chrome OS.

  13. Re:ahahahaha by stephanruby · · Score: 2, Interesting

    What won't it do to convince you that you need to do something half way across the world using systems under their control, what you once did perfectly in your office?

    You've obviously never printed something remotely to Kinkos. That feature is convenient and can be a life-saver sometimes.

    This doesn't mean that everyone will start printing remotely 100% of the time, but personally, I'd be glad to have this feature -- even if I only very rarely use it. If Google made it easy enough, I could see myself printing from my phone, from my television set up box, and whenever I'm away from my home or office, or my printer is broken, or my printer doesn't support the colors I want, the particular size, or the quantities of copies I want.

    Also, this means that Google could lower the barrier of entry for every mom and pop printer store out there to be able to work like Kinkos, and this should facilitate economies of scales and reduce the cost of printing (Kinkos is nice, but its prices can really be high sometimes).