Abstract: Module management software receives a request from the browser for a presentation composed of at least one module. The module management software transmits a request for module data associated with the module to a first server that caches the module data after retrieving the module data from a website. The module management software then receives the requested module data from the first server and transmits a request for each of the resource files described in the module data to a second server that caches each of the resource files after retrieving the resource file from an external (or internal) website. Each request for a resource file can be handled by a corresponding thread. The module management software delays transmission of the module data to the browser, if any requested resource file is not received within a time limit derived at least in part from a service level agreement.

Abstract: Module management software receives a request from the browser for a presentation composed of at least one module. The module management software transmits a request for module data associated with the module to a first server that caches the module data after retrieving the module data from a website. The module management software then receives the requested module data from the first server and transmits a request for each of the resource files described in the module data to a second server that caches each of the resource files after retrieving the resource file from an external (or internal) website. Each request for a resource file can be handled by a corresponding thread. The module management software delays transmission of the module data to the browser, if any requested resource file is not received within a time limit derived at least in part from a service level agreement.