by Kin Lane on 08 Feb, 2011
The whole point of deploying a Google Cloud Print Proxy is to be able to manage print jobs.After authenticating using Google ClientLogin API, you can then fetch an existing Google Cloud Print Job from the users queue. Each print job has an ID that you can use to reference the print job and control the status with /control service. The Google Cloud Print /control endpoint accepts the following parameter(s): '
- jobid - Unique job identification (generated by server).
- status - Status of the job, which can be one of the following:
- QUEUED: Job just added and has not yet been downloaded.
- SPOOLED: Job downloaded and has been added to the client-side native printer queue.
- DONE: Job printed successfully.
- ERROR: Job cannot be printed due to an error.
- code - Error code string or integer (as returned by the printer or OS) if the status is ERROR.
- message - Error message string (as returned by the printer or OS) if the status is ERROR
- Introduction to the Google Cloud Print Services Interface (kinlane.com)
- Solving Windows 7 Print Spooler Problems (brighthub.com)
- Print From iOS and Android to Any Printer with Google Cloud Print (wired.com)
Network of Sites
Latest Blog Posts
- I Am Speaking At The Dallas-Forth Worth API Professionals Meetup May 14th
- A Civic Hacker Corp
- Hacking Your Automobile Dashboard
- A Lifetime of Experience with 'Government Workers'
- Reminder of Why Data Portability Should Be Default: Bye Bye Posterous
- An Author Walk-Through of a Story in Audio
- Who Are The Customers For Your Startup?
- Your Glasses Are Prime Real Estate for a Human Computer Interaction (HCI)
- Personal Legal Storage Locker for TOS and NDA
- Add Or Update Your #ReclaimOpen Profile At The Github Site