Abstract: In one example, a printer address for a network-connected printer, a printer location, and an identifier for a mobile computing device are received. Responsive to receiving a message that is sent to the printer address and that includes a print job, the print job is stored. The identifier is sent to a tracker computing device. A mobile device location is received from the tracker device. Responsive to determining a calculated distance between the mobile device and the printer is less than or equal to a trigger distance, the print job is sent to the printer.

Abstract: In one example, a cloud-based printing service that calculates cumulative usage data of a consumable.

Abstract: In one example, a printer consumable is locked to a content provider. A document that includes content restricted by a provider is printed if the printer consumable is installed in the printer.

Abstract: A method includes, with a physical computing system, executing a navigational application for a printer interface of a printer connected to the physical computing system through a network, with the physical computing system, using a content model for the navigational application, the content model defining attributes and a category for a screen. The method further includes, with the physical computing system, receiving content associated with the category, and with the physical computing system, providing to the printer the screen and the content in a format that is executable by the printer.

Abstract: In one embodiment, a registry of network-connected printers that are members of a social print group is maintained at a computer system. Content is obtained. A request is received from a first network-connected printer that is a member of the group, the request to provide the content to a second network-connected printer that is a member of the group. The content is provided to the second printer in response to the request.

Abstract: In one embodiment, first content is received, via an email address from which printable content is received from a plurality of computing devices, from a network-connected computing device. The first content is stored. An access code is sent to the publisher device. The code is received from a network-connected printer. The code is compared to a database or registry that associates the access code with the first content. The first content is caused to be rendered. The rendered first content is sent to the printer for printing.

Abstract: In one embodiment, a first assignment is received. The first assignment is an assignment of a category tag to first content accessible via a first printer application. A second assignment is received. The second assignment is an assignment of the category tag to second content accessible via a second printer application. The first and second assignments are stored. Functionality to facilitate retrieval of content via the assignments is provided to a network-connected printer. A request to print selected content from among the first and second content is received. Responsive to the request, the selected content is retrieved, raster processed, and sent to the printer.

Abstract: In one embodiment, a registry of network-connected printers that are members of a social print group is maintained at a computer system. Content is obtained. A request is received from a first network-connected printer that is a member of the group, the request to provide the content to a second network-connected printer that is a member of the group. The content is provided to the second printer in response to the request.

Abstract: In one embodiment, a registry of network-connected printers that are members of a social print group is maintained at a computer system. Content is obtained. A first request is received from a first printer that is a member of the group. The first request is a request to share the content with a second printer that is a member of the group. A communication that the content is accessible at the second printer is sent. A second request is received from the second printer. The second request is a request to provide the content to the second printer. Content is provided to the second printer.

Abstract: A web service request is received by an intermediary that performs a conversion of the requestor's service interface to the service interface supported by a service provider matching the requested service, then invokes that service. A reverse conversion is performed when passing a reply to the requester. The web serving intermediary maintains a library of each target service in terms of the target service's tModel and on its binding protocol support. The intermediary receives web service requests from requesters including their source tModel and target web service information. The intermediary identifies a mapping aspect to invoke the target web service from the aspect library. The target service tModel is embodied in the mapping aspect which is weaved into the code invoking the target service at runtime. In this way, the interface logic is decided at run time.

Abstract: A web service request is received by an intermediary that performs a conversion of the requestor's service interface to the service interface supported by a service provider matching the requested service, then invokes that service. A reverse conversion is performed when passing a reply to the requester. The web serving intermediary maintains a library of each target service in terms of the target service's tModel and on its binding protocol support. The intermediary receives web service requests from requesters including their source tModel and target web service information. The intermediary identifies a mapping aspect to invoke the target web service from the aspect library. The target service tModel is embodied in the mapping aspect which is weaved into the code invoking the target service at runtime. In this way, the interface logic is decided at run time.

Abstract: A web service request is received by an intermediary that performs a conversion of the requestor's service interface to the service interface supported by a service provider matching the requested service, then invokes that service. A reverse conversion is performed when passing a reply to the requester. The web serving intermediary maintains a library of each target service in terms of the target service's tModel and on its binding protocol support. The intermediary receives web service requests from requestors including their source tModel and target web service information. The intermediary identifies a mapping aspect to invoke the target web service from the aspect library. The target service tModel is embodied in the mapping aspect which is weaved into the code invoking the target service at runtime. In this way, the interface logic is decided at run time.

Abstract: A web service request is received by an intermediary that performs a conversion of the requestor's service interface to the service interface supported by a service provider matching the requested service, then invokes that service. A reverse conversion is performed when passing a reply to the requester. The web serving intermediary maintains a library of each target service in terms of the target service's tModel and on its binding protocol support. The intermediary receives web service requests from requestors including their source tModel and target web service information. The intermediary identifies a mapping aspect to invoke the target web service from the aspect library. The target service tModel is embodied in the mapping aspect which is weaved into the code invoking the target service at runtime. In this way, the interface logic is decided at run time.