Google Cloud Print Registration Includes Publishing

Should we upload the new set of defaults when they change Or should we maintain a separate set of defaults in the cloud If so, we need server-side UI to change defaults.

A cloud print proxy enables cloud printing support for legacy (non-cloud-aware) printers.

The proxy acts as a protocol bridge between Google Cloud Print and the native print driver stack on existing PCs.

The cloud print proxy runs on Windows (XP SP2 and higher), Mac OS X (10.5 and higher on Intel), and Linux desktops and laptops.

The proxy code is built as a part of the Google Chrome browser and is an end-user opt-in feature.

It should be noted that in parallel to developing the cloud print proxy for legacy printer support, Google will be working with third parties to help create solutions (based on opendocumented standards) for allowing printers to connect directly to Google Cloud Print without the need for a dedicated PC or cloud print proxy on that PC.

This document is intended for Google Chrome browser developers as well as future implementers of the service interfaces (for example, printer vendors).

When the user chooses to enable this feature, the proxy code asks for the users Google account credentials (if this has not already been entered for another cloud-related feature such as Bookmarks Sync).

Upon successful authentication, the client proxy code runs a background thread that performs the following steps.

It then requests Google Cloud Print for a list of printers already registered to this specific proxy for this specific user.

Google Cloud Print Registration Includes Publishing

Printer registration includes publishing the capabilities as well as printer default settings for each printer in an extensible format.

Printer registration follows the steps outlined in the service interfaces document.

Pending jobs are downloaded and spooled to the local printer.

Print request notifications are delivered using the XMPP protocol.

Upon receiving a print request, the proxy fetches the print jobs for that specific proxy from Google Cloud Print and spools them to the local printer.

The printer notification code above checks for changes to the status of the job and updates Google Cloud Print with the status of the job.

The platform-dependent code is abstracted behind a platform-agnostic interface.

Users enter their Google credentials only once to enable one or more of these features.

In addition, upon user login, an invisible instance of this process with this background thread running is launched automatically.

The format used for the user-selected printer settings (print ticket) on each platform is also listed in this table.

On Windows, the proxy code will use a PDF interpreter library to print the PDF.

The proxy code leverages platform support on Mac OS X and Linux to print PDF documents.

Google Cloud Print supports multiple formats and the actual data formats used for cloud-aware printers will likely be different from the ones listed below.

Google Cloud Print For Mac Os X