# US 2014/0207848 A1 · Client-side aggregation of nested resource dependencies

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0207848 A1
- Document ID: US20140207848A1
- Status: Published application
- Kind: A1
- Application number: 14/072,407
- Filed: 2013-11-05
- Published: 2014-07-24
- Earliest claimed: 2013-01-23
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Charles E. DUMONT; Dan DUMONT
- Web page: https://patentgrep.com/patent/US20140207848A1

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F 9/44521: {Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A computer-implemented method, system, and/or computer program product retrieves a nested resource. A client computer identifies software modules that are required by a primary software module. The dependent and primary software modules are consolidated at a client computer into an aggregated software module, which is a nested resource. A request for the aggregated software module is transmitted to a module server from a client-side module loader, which is incapable of identifying a name of received software modules from the module server. The client-side module loader in the client computer then receives the requested aggregated software module without any identification.

## Claims

### Claim 1

A computer-implemented method of retrieving a nested resource of software modules, the computer-implemented method comprising:
identifying, by a client computer, dependent software modules that are required by a software module;
consolidating, by the client computer, the software module with the dependent software modules to generate an aggregated software module, wherein the aggregated software module is a nested resource of software modules;
transmitting, from a client-side module loader in the client computer to a module server, a request for the aggregated software module, wherein the client-side module loader is incapable of identifying a name of received software modules from the module server, and wherein the module server is blocked from returning additional software modules in response to a request for a particular module; and
receiving, by the client-side module loader in the client computer, a requested aggregated software module, wherein the requested aggregated software module has no identification.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising:
populating, by the client-side module loader, a software framework with the requested aggregated software module.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, further comprising:
utilizing, by the client-side module loader, asynchronous module definition (AMD) specification commands to define and consolidate the software module with the dependent software modules to generate the aggregate software module, wherein the AMD specification commands comprise a “define” command to identify the dependent software modules that are required by the software module, and wherein the AMD specification commands further comprise a “require” command to consolidate the software module with the dependent software modules to generate the aggregated software module.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3, wherein the module server recognizes the aggregated software module using AMD specification commands without any plugins.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising:
in response to the client-side module loader determining that a particular dependent software module from the dependent software modules has been previously loaded onto the client computer, removing the particular dependent software module from the aggregated software module before transmitting the request for the aggregated software module to the module server.
