Scheduling of software updates
Software updates are described. In an implementation, a method includes forming an authentication request to be communicated to an authentication service over a network that includes a version identifier of at least one application module of a client. A response is received to the authentication request which includes an indication of whether an update is available for the at least one application module and a token that verifies the authentication.
1 . A method comprising:
forming an authentication request to be communicated to an authentication service over a network that includes a version identifier of at least one application module of a client; and
receiving a response to the authentication request which includes an indication of whether an update is available for the at least one application module and a token that verifies the authentication.
2 . A method as described in claim 1 , wherein the token is configured for use in accessing a plurality of service providers over the network without providing authentication data to each said service provider.
3 . A method as described in claim 1 , wherein an update schedule is used, at least in part, to determine whether to indicate that an update is available for the at least one application module.
4 . A method as described in claim 3 , wherein:
the indication matches the version number when the determination is made to indicate that the update is not available.
the indication is an updated version of the version identifier when the determination is made to indicate that the update is available.
5 . A method as described in claim 3 , wherein the update schedule controls how many said responses include indications which indicate that the update is available are provided during a period of time.
6 . A method as described in claim 3 , wherein the update schedule is configured as a ratio that describes how many said responses include indications that the update is available.
7 . A method as described in claim 1 , further comprising:
when the indication in the response indicates that the update is available, initiating a thread to perform a download of the update in a background during execution of the at least one application module; and
when the at least one application module is reinitiated, applying the update to the at least one application module.
8 . A method comprising:
determining whether to indicate that an update is available for an application module of a client based on an update schedule; and
forming a response to be communicated to the client over a network that indicates whether the update is available based on the determination.
9 . A method as described in claim 8 , wherein:
the determining is performed in response to receipt of a request from the client; and
the request includes a version identifier of the application module.
10 . A method as described in claim 9 , wherein the request is part of a single authentication request that is utilized to verify the identity of the client, such that, the client may access a plurality of service providers over the network without providing authentication data to each said service provider.
11 . A method as described in claim 9 , wherein the indication in the response matches a version identifier of the application module of the client when the determination is made to indicate that the update is not available.
12 . A method as described in claim 9 , wherein the indication in the response is a version identifier that is an updated version of the version identifier of the application module of the client when the determination is made to indicate that the update is available.
13 . A method as described in claim 8 , further comprising determining whether the update is available for the application module and wherein the determining whether to indicate that the update is available is not performed when the update is not available.
14 . A method comprising:
receiving a version identifier of an application module;
when an update is available for the application module based on the version identifier, determining whether to indicate that the update is available based on an update schedule that controls how many of a plurality of said indications indicate that the update is available; and
forming a response based the determining.
15 . A method as described in claim 14 , wherein:
the version identifier is includes as part of an authentication request received from a client over a network; and
the receiving, the determining and the forming are performed by an authentication service.
16 . A method as described in claim 15 , wherein the authentication request that is utilized to verify the identity of the client, such that, the client may access a plurality of service providers over the network without providing authentication data to each said service provider.
17 . A method as described in claim 14 , wherein the update schedule is configured as a ratio that describes how many said indications indicate that the update is available.
18 . A method as described in claim 14 , wherein the update schedule controls how many said indications indicate that the update is available are provided during a period of time.
19 . A method as described in claim 14 , wherein the indication matches the received version identifier when the determination is made to indicate that the update is not available.
20 . A method as described in claim 14 , wherein the indication is an updated version of the receiver version identifier when the determination is made to indicate that the update is available.