Abstract: At a client computer, a web browser is connected to a local web server. The local web server is coupled with a local utility executing on the client computer that is distinct from the web browser. The web browser sends, to the local web server via a first communications channel, a first open-ended message that does not require a return message. The local web server waits until the local utility determines there is information to be provided to the web browser and sends, via the first communications channel, a first return message responsive to the first open-ended message. The web browser, in response to and upon receiving the first return message responsive, maintains communication with the local web server by sending, using a second communications channel distinct from the first communications channel, a second open-ended message that does not require a return message to the local web server.

Abstract: At a client computer, a web browser is connected to a local web server. The local web server is coupled with a local utility executing on the client computer that is distinct from the web browser. The web browser sends, to the local web server via a first communications channel, a first open-ended message that does not require a return message. The local web server waits until the local utility determines there is information to be provided to the web browser and sends, via the first communications channel, a first return message responsive to the first open-ended message. The web browser, in response to and upon receiving the first return message responsive, maintains communication with the local web server by sending, using a second communications channel distinct from the first communications channel, a second open-ended message that does not require a return message to the local web server.

Abstract: A client computer includes a web browser connected to a local web server that is coupled with a local utility. Upon loading a web page, the web browser sends, to the local web server, a first open-ended message that does not require a return message from the local web server. In response to and upon receiving a response to the first open-ended message, the web browser maintains communication with the local web server by sending a second open-ended message that does not require a return message to the local web server. The local web server receives the first open-ended message, waits until the local utility determines that there is information to be provided to the web browser, and in response to determining that there is information to be provided to the web browser, sends a first return message including the information to the web browser.

Abstract: A client computer includes a web browser connected to a local web server that is coupled with a local utility. Upon loading a web page, the web browser sends, to the local web server, a first open-ended message that does not require a return message from the local web server. In response to and upon receiving a response to the first open-ended message, the web browser maintains communication with the local web server by sending a second open-ended message that does not require a return message to the local web server. The local web server receives the first open-ended message, waits until the local utility determines that there is information to be provided to the web browser, and in response to determining that there is information to be provided to the web browser, sends a first return message including the information to the web browser.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for controlling a local utility are disclosed. A first request originating from an application and including a first token is received at a local utility. The application received a web page, including a plurality of links and the first token, from a first server. The plurality of links are received by the application from a second server. The first token is authenticated. Authentication includes sending the first token to a third server. In response to authenticating the first token, a second token is generated at the local utility. The second token is sent to the application for inclusion in subsequent requests from the application.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for controlling a local utility are disclosed. A first request originating from an application and including a first token is received at a local utility. The application received a web page, including a plurality of links and the first token, from a first server. The plurality of links are received by the application from a second server. The first token is authenticated. Authentication includes sending the first token to a third server. In response to authenticating the first token, a second token is generated at the local utility. The second token is sent to the application for inclusion in subsequent requests from the application.

Abstract: At a client computer, a web browser displays a control for a local utility executed on the client computer, wherein the control includes a link. The web browser receives a user input selecting the control and, in response to the user input, issues a request through the link to a local web server coupled with the local utility. The link includes a domain that resolves to a loopback network address. The loopback network address is a self-referencing address for the local web server at the client computer. The local web server receives the request and provides the local utility with a command portion of the request. In response to receiving the command portion of the request from the local web server, the local utility takes one or more actions based on the command portion of the request.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for controlling a local utility are disclosed. A first request originating from an application and including a first token is received at a local utility. The application received a web page, including a plurality of links and the first token, from a first server. The plurality of links are received by the application from a second server. The first token is authenticated. Authentication includes sending the first token to a third server. In response to authenticating the first token, a second token is generated at the local utility. The second token is sent to the application for inclusion in subsequent requests from the application.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for controlling a local utility are disclosed. A first request originating from an application and including a first token is received at a local utility. The application received a web page, including a plurality of links and the first token, from a first server. The plurality of links are received by the application from a second server. The first token is authenticated. Authentication includes sending the first token to a third server. In response to authenticating the first token, a second token is generated at the local utility. The second token is sent to the application for inclusion in subsequent requests from the application.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for controlling a local utility are disclosed. A first request originating from an application and including a first token is received at a local utility. The application received a web page, including a plurality of links and the first token, from a first server. The plurality of links are received by the application from a second server. The first token is authenticated. Authentication includes sending the first token to a third server. In response to authenticating the first token, a second token is generated at the local utility. The second token is sent to the application for inclusion in subsequent requests from the application.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for controlling a local utility are disclosed. A first request originating from an application and including a first token is received at a local utility. The application received a web page, including a plurality of links and the first token, from a first server. The plurality of links are received by the application from a second server. The first token is authenticated. Authentication includes sending the first token to a third server. In response to authenticating the first token, a second token is generated at the local utility. The second token is sent to the application for inclusion in subsequent requests from the application.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for controlling a local utility are disclosed. A first request originating from an application and including a first token is received at a local utility. The application received a web page, including a plurality of links and the first token, from a first server. The plurality of links are received by the application from a second server. The first token is authenticated. Authentication includes sending the first token to a third server. In response to authenticating the first token, a second token is generated at the local utility. The second token is sent to the application for inclusion in subsequent requests from the application.