Abstract: Techniques are described for managing preloading of data for client computing systems. A client computing system may provide one or more persistent data storage caches on local storage, such as to support a particular software program executing on the client computing system (e.g., a Web browser program, with the persistent data storage cache designed to store browser cookies and other data for later access by the Web browser program). Additional data may be stored in such a persistent data storage cache by preloading those data groups before they are requested by the client computing system (e.g., based on interactions of a user of the client computing system with an executing program on the client computing system). Particular data groups to preload may be selected in various manners, including to provide a specified type of minimum functionality to a client computing system based on the preloaded data groups.

Abstract: Techniques are described for managing preloading of data for client computing systems. A client computing system may provide one or more persistent data storage caches on local storage, such as to support a particular software program executing on the client computing system (e.g., a Web browser program, with the persistent data storage cache designed to store browser cookies and other data for later access by the Web browser program). Additional data may be stored in such a persistent data storage cache by preloading those data groups before they are requested by the client computing system (e.g., based on interactions of a user of the client computing system with an executing program on the client computing system). Particular data groups to preload may be selected in various manners, including to provide a specified type of minimum functionality to a client computing system based on the preloaded data groups.

Abstract: Aspects of the present disclosure relate to the generation and delivery of content including unique and shared components. A content delivery network service provider can obtain requests for content from client computing devices. Based on information provided in the request or otherwise managed by executable code on the client computing device, the CDN service provider obtains one or more pieces of content that may be shared by more than one user or client computing devices. Additionally, the CDN service provider obtains one or more pieces of content that will not be shared by more than one user or more than one client computing device. Responsive to the content request, the CDN service provider can combine the one or more pieces of shared content and the one or more pieces of unique content and deliver the combined content to the requested client computing device.

Abstract: Techniques are described for managing cached data in a network environment. In one example, the techniques include receiving a client request for a data group, determining that a cached copy of the requested data group that is stored in the persistent cache storage is no longer valid relative to a current copy of the data group stored at a remote data source system, obtaining from the remote data source system information about differences between the cached copy and the current copy and instructions associated with the identified differences, modifying, by the configured server computing system, the cached copy to include the identified differences in accordance with the received instructions, and providing, by the configured server computing system, the modified cached copy of the requested data group to the client in response to the client request.

Abstract: Techniques are described for managing cached data in a network environment. In one example, the techniques include receiving a client request for a data group, determining that a cached copy of the requested data group that is stored in the persistent cache storage is no longer valid relative to a current copy of the data group stored at a remote data source system, obtaining from the remote data source system information about differences between the cached copy and the current copy and instructions associated with the identified differences, modifying, by the configured server computing system, the cached copy to include the identified differences in accordance with the received instructions, and providing, by the configured server computing system, the modified cached copy of the requested data group to the client in response to the client request.

Abstract: Techniques are described for managing cached data in a network environment. In one example, the techniques include receiving a client request for a data group, determining that a cached copy of the requested data group that is stored in the persistent cache storage is no longer valid relative to a current copy of the data group stored at a remote data source system, obtaining from the remote data source system information about differences between the cached copy and the current copy and instructions associated with the identified differences, modifying, by the configured server computing system, the cached copy to include the identified differences in accordance with the received instructions, and providing, by the configured server computing system, the modified cached copy of the requested data group to the client in response to the client request.

Abstract: Techniques are described for managing preloading of data for client computing systems. A client computing system may provide one or more persistent data storage caches on local storage, such as to support a particular software program executing on the client computing system (e.g., a Web browser program, with the persistent data storage cache designed to store browser cookies and other data for later access by the Web browser program). Additional data may be stored in such a persistent data storage cache by preloading those data groups before they are requested by the client computing system (e.g., based on interactions of a user of the client computing system with an executing program on the client computing system). Particular data groups to preload may be selected in various manners, including to provide a specified type of minimum functionality to a client computing system based on the preloaded data groups.

Abstract: Techniques are described for managing preloading of data for client computing systems. A client computing system may provide one or more persistent data storage caches on local storage, such as to support a particular software program executing on the client computing system (e.g., a Web browser program, with the persistent data storage cache designed to store browser cookies and other data for later access by the Web browser program). Additional data may be stored in such a persistent data storage cache by preloading those data groups before they are requested by the client computing system (e.g., based on interactions of a user of the client computing system with an executing program on the client computing system). Particular data groups to preload may be selected in various manners, including to provide a specified type of minimum functionality to a client computing system based on the preloaded data groups.

Abstract: Techniques are described for managing data transmissions between computing systems based at least in part on using a streaming transport protocol. At least some such data transmissions may be performed using HTTP, with one or more underlying transport protocols used to implement the HTTP-based data transmissions. HTTP-based data transmissions performed using an underlying streaming transport protocol, for example, may send data without performing error detection for reliability and without ensuring ordered delivery of the sent data. In addition, one or more HTTP-based data transmissions may be initiated using an underlying streaming transport protocol, but subsequent data transmissions may switch to using a different underlying transport protocol (e.g., TCP) or different transmission technique that is performed without using data streaming.

Abstract: Techniques are described for managing data transmissions between computing systems based at least in part on using a streaming transport protocol. At least some such data transmissions may be performed using HTTP, with one or more underlying transport protocols used to implement the HTTP-based data transmissions. HTTP-based data transmissions performed using an underlying streaming transport protocol, for example, may send data without performing error detection for reliability and without ensuring ordered delivery of the sent data. In addition, one or more HTTP-based data transmissions may be initiated using an underlying streaming transport protocol, but subsequent data transmissions may switch to using a different underlying transport protocol (e.g., TCP) or different transmission technique that is performed without using data streaming.

Abstract: Techniques are described for managing data transmissions between computing systems based at least in part on using a streaming transport protocol. At least some such data transmissions may be performed using HTTP, with one or more underlying transport protocols used to implement the HTTP-based data transmissions. HTTP-based data transmissions performed using an underlying streaming transport protocol, for example, may send data without performing error detection for reliability and without ensuring ordered delivery of the sent data. In addition, one or more HTTP-based data transmissions may be initiated using an underlying streaming transport protocol, but subsequent data transmissions may switch to using a different underlying transport protocol (e.g., TCP) or different transmission technique that is performed without using data streaming.

Abstract: A method is disclosed that includes receiving a request for a transaction from a customer at a seller server system via an electronic-commerce website and identifying a customer account stored at the seller server system based on an identity of the customer. A plurality of financial instruments is associated with the customer account. The plurality of financial instruments has a customer-specific sequence including at least a first financial instrument pre-selected by the customer and a second financial instrument. The method includes automatically attempting to collect a particular payment associated with the transaction from a first financial service provider corresponding to the first financial instrument and automatically attempting to collect the particular payment from a second financial service provider corresponding to the second financial instrument in response to data received at the seller server system indicating a denial of the payment.

Abstract: A method is disclosed that includes receiving a request for a transaction from a customer at a seller server system via an electronic-commerce website and identifying a customer account stored at the seller server system based on an identity of the customer. A plurality of financial instruments is associated with the customer account. The plurality of financial instruments has a customer-specific sequence including at least a first financial instrument pre-selected by the customer and a second financial instrument. The method includes automatically attempting to collect a particular payment associated with the transaction from a first financial service provider corresponding to the first financial instrument and automatically attempting to collect the particular payment from a second financial service provider corresponding to the second financial instrument in response to data received at the seller server system indicating a denial of the payment.