Auto-updating an application without requiring repeated user authorization
First Claim
Patent Images
1. A method comprising:
- at a client system,installing a loader application and an associated dynamic link library on the client system, wherein the loader application and the dynamic link library comprise a single client application and the dynamic link library includes a function that sends a request to a location external to the client system for auto-updates to the dynamic link library;
upon a first execution of the loader application, receiving a user authorization for the client application to communicate with locations external to the client system via a communications network, wherein receiving the user authorization includes triggering a firewall on the client system;
in accordance with the user authorization, auto-updating the dynamic link library and not the loader application;
in accordance with a determination that the loader application remains unchanged, enabling the client application to continue to communicate with locations external to the client system via the communications network without requiring additional user authorization; and
repeating the auto-updating during one or more executions of the loader application subsequent to the first execution, wherein repeating auto-updating the dynamic link library does not trigger the firewall on the client system.
2 Assignments
0 Petitions
Accused Products
Abstract
A loader application and an associated dynamic link library are installed on a client system. Upon a first execution of the loader application, a user authorization to communicate with locations external to the client via a communications network is received. The dynamic link library and not the loader application is auto-updated without requiring additional user authorization. The auto-updating is repeated during one or more executions of the loader application subsequent to the first execution.
-
Citations
15 Claims
-
1. A method comprising:
-
at a client system, installing a loader application and an associated dynamic link library on the client system, wherein the loader application and the dynamic link library comprise a single client application and the dynamic link library includes a function that sends a request to a location external to the client system for auto-updates to the dynamic link library; upon a first execution of the loader application, receiving a user authorization for the client application to communicate with locations external to the client system via a communications network, wherein receiving the user authorization includes triggering a firewall on the client system; in accordance with the user authorization, auto-updating the dynamic link library and not the loader application; in accordance with a determination that the loader application remains unchanged, enabling the client application to continue to communicate with locations external to the client system via the communications network without requiring additional user authorization; and repeating the auto-updating during one or more executions of the loader application subsequent to the first execution, wherein repeating auto-updating the dynamic link library does not trigger the firewall on the client system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A client comprising:
-
one or more processors; memory storing one or more programs to be executed by the one or more processors, the one or more programs including; a client application installed on the client, comprising; a loader application installed on the client, which when executed for a first time, initiates receipt of a user authorization for the client application to communicate with locations external to the client, wherein a firewall is triggered on the client when the loader application initiates receipt of the user authorization; and a dynamic link library associated with the loader application installed on the client, wherein the dynamic link library includes a function that sends a request to a location external to the client for auto-updates to the dynamic link library, the dynamic link library and not the loader application is auto-updated without requiring additional user authorization, the client application, in accordance with a determination that the loader application remains unchanged, is enabled to continue to communicate with locations external to the client, and at least portions of the dynamic link library are auto-updated during one or more executions of the loader application subsequent to the first execution, wherein the firewall is not triggered on the client when the dynamic link library is auto-updated during the one or more executions. - View Dependent Claims (10, 11, 12, 13, 14, 15)
-
Specification