US20050273766A1 - Application program caching - Google Patents
Application program caching Download PDFInfo
- Publication number
- US20050273766A1 US20050273766A1 US11/186,274 US18627405A US2005273766A1 US 20050273766 A1 US20050273766 A1 US 20050273766A1 US 18627405 A US18627405 A US 18627405A US 2005273766 A1 US2005273766 A1 US 2005273766A1
- Authority
- US
- United States
- Prior art keywords
- computing device
- application program
- component
- caching
- cached
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5033—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering data affinity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/509—Offload
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Application program caching and execution is disclosed. An application program component, which may constitute the only component of an application program, is cached by a computing device from an original computing device. The computing device executes the cached component in lieu of its execution by the original computing device. The computing device may be a client computing device, where the client device executes the cached component for itself. The computing device may also be a caching computing device, where the caching device executes the cached component for the client computing device.
Description
- The present application is related to and claims the benefit and priority of the earlier filed provisional patent application entitled “Caching and Distributed Execution of Web Applications”[docket no. 154795.2], filed on Jul. 11, 2000, and assigned Ser. No. 60/217,602.
- This invention relates generally to application programs executed by an original computing device for a client computing device, and more particularly to programs downloaded from the original device, cached, and executed for the client computing device by the client device and/or a caching computing device.
- Traditionally, application programs have been executed locally by client computing devices. These programs include a wide variety of consumer- and business-related programs, such as word processing programs, accounting programs, personal information management (PIM) programs, and other types of programs. One of the advantages of executing programs locally has been and continues to be that the programs run as fast as the hardware of the client computing devices allows.
- With the increasing popularity of network computing over networks such as the Internet, more attention has been given to application programs that are executed by another computing device for client computing devices. For example, an application service provider (ASP) may offer a subscription service in which an application program is executed for subscribing clients by the ASP's server. The subscribing clients utilize the program over the Internet. Input and output is typically performed at the clients, while the execution of the program usually occurs at the server.
- This model has some advantages. For example, small businesses that may not have adequate information technology (IT) departments can instead effectively outsource some or all of their application program needs to ASP's. This means that the the businesses do not have to concern themselves with maintaining and updating the programs. Instead, nearly everything is handled by the ASP's. Moreover, rather than paying for program licenses, businesses instead pay on a subscription basis, which can be desirable.
- Executing application programs by another computing device for client computing devices has disadvantages as well. One disadvantage is that the programs usually run slower than if executed by the client computing devices themselves. This is because the computing device hosting the application programs may have to run a number of instances of the programs for a number of different client computing devices. Even if the computing device hosting the application program can sufficiently handle this load, network latency can affect the speed at which the programs run. The fastest Internet connections are still typically slower than the internal speeds at which a computer runs. Congestion within the Internet can also affect the speed with which client computing devices interact with application programs executed by another computing device. For these and other reasons, there is a need for the present invention.
- The invention provides caching and executing an application program by a client computing device or a caching computing device. In accordance with the present invention, an entire application program may be cached, or only a portion of the application program may be cached. A client computing device, a caching computing device, or both devices, are used to cache the application program. The devices cache the application program from an original computing device. Where the application program or a portion thereof is cached at the client computing device, the client computing device executes the cached application programs for itself or the cached portion. If the application program or a portion thereof is cached at a caching device, the caching computing device executes the cached application program or the cached portion for the client computing device. A portion of the application program may also reside in the original computing device, which also executes this portion of the application program for the client computing device.
- In accordance with the present invention, the client computing device generates a request for an application program to be executed by the original computing device for the client computing device. If the client computing device has the capability to cache the application program, it intercepts and examines the request to determine if the request relates to any application program that it has already cached. If so, then the request is redirected to a cached application program for execution by the client computing device itself. Otherwise, the client computing device passes the request to a caching computing device or an original computing device.
- If a caching computing device having application caching capability is present, it intercepts and examines the requested passed to it by the client computing device to determine if the request relates to any application program that it has already cached. If so, then the request is redirected to a cached application program for execution by the caching computing device for the client computing device. Otherwise, the caching computing device passes the request to an original computing device, which fulfills the request by executing the requested application program for the client computing device.
- Application caching is different from content caching. Content caching is limited to the storage of data at a location closer to a client computing device than the original storage location. When the client computing device desires to access the content, it ultimately receives the content from the closer location. This is presumably faster than receiving the content from the more distant location. Content caching is a relatively simple process. The computing devices that are storing the content do not actually execute anything. The devices exist only to serve the content to client computing devices, while the client computing devices themselves may wholly execute some of the content.
- Conversely, application caching involves downloading and installing at least a part of an application program on a caching computing device. The caching computing device is compatible with the original computing device. Configuration parameters are downloaded and interpreted by the caching computing device to determine how to install the program. Unlike a content caching computing device that only serves content to client computing devices, an application caching computing device executes at least part of an application program for the client computing devices. No execution of the data is typically performed by a content caching computing device.
- The invention includes computer-implemented methods, machine-readable media, computerized systems, and computers of varying scopes. Other aspects, embodiments and advantages of the invention, beyond those described here, will become apparent by reading the detailed description and with reference to the drawings.
-
FIG. 1 is a diagram showing the basic configuration of a client computing device, a caching computing device, and an original computing device, according to preferred embodiments of the invention; -
FIG. 2 is a diagram showing a more specific example of the configuration of FIG. in which the client computing device is communicatively connected to the caching computing device through a local network, and the caching computing device is communicatively connected to the original computing device through a remote network, according to an embodiment of the invention; -
FIG. 3 is a diagram showing another more specific example of the configuration ofFIG. 1 , in which the client, caching, and original computing devices are communicatively connected to one another through the same network, according to an embodiment of the invention; -
FIG. 4 is a diagram showing the caching computing device ofFIG. 1 in more detail, according to an embodiment of the invention; -
FIG. 5 is a diagram showing how a device, such as the client computing device or the caching computing device, intercepts, passes through, and redirects application program requests, according to an embodiment of the invention; -
FIG. 6 is a diagram showing the client computing device ofFIG. 1 in more detail, according to an embodiment of the invention; -
FIG. 7 is a flowchart of a method summarizing how the client, caching, and original computing devices handle an application program request; -
FIG. 8 is a flowchart of a method summarizing how the client computing device or the caching computing device determines whether part or all of an application program should be cached; -
FIG. 9 is a flowchart of a method showing how a client computing device or a caching computing device downloads and installs an application program, or an application program component, for local execution, according to an embodiment of the invention; and, -
FIG. 10 is a diagram of an example computing device, which may implement any of the caching, client, or original computing devices ofFIG. 1 . - In the following detailed description of exemplary embodiments of the invention, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific exemplary embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be utilized, and logical, mechanical, electrical, and other changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
- The diagram 100 of
FIG. 1 illustrates the basic configuration for preferred embodiments of the invention. Aclient computing device 102 is communicatively connected to acaching computing device 104 through afirst network 106. Thecaching computing device 104 is communicatively connected to anoriginal computing device 108 through asecond network 110. Each of thecomputing devices devices FIG. 1 for illustrative clarity. - A cacheable application program is initially installed only on the
original computing device 108. The application program can be any type of business- or consumer-related application program. Examples of application programs include word processing programs, spreadsheet programs, communication programs, and other kinds of programs. Thecaching computing device 104 has cached all or part of the cacheable application program, and executes the cached portion of the application program for theclient computing device 102. If part of the application program is not cached by thecaching computing device 104 but remains at the original computing device, then theoriginal computing device 108 executes this portion of the program for theclient computing device 102. Theclient computing device 102 can also cache and execute a portion of the application program for itself. - The application program may be partitioned into different parts that are executed by one or all of the
client computing device 102, thecaching computing device 104, or theoriginal computing device 108, depending on each device's characteristics. Graphical user interface aspects of the program may be cached at and executed directly by theclient computing device 102. The bulk of the non-graphical user interface aspects of the program may be cached at and executed by thecaching computing device 104 for theclient computing device 102. Theoriginal computing device 108 may only execute rarely used aspects of the application program for theclient computing device 102. - The
first network 106 and thesecond network 110 can be different networks, or the same network. Examples of networks include local-area networks (LAN's), wide-area network (WAN's), intranets, extranets, the Internet, local networks, remote networks, and other types of networks.FIG. 2 shows a diagram 200 of a specific embodiment of the configuration ofFIG. 1 . Thenetwork 106 ofFIG. 1 is a local network inFIG. 2 , as denoted byreference number 206, and thenetwork 110 ofFIG. 1 is a remote network, as denoted byreference number 210. Thelocal network 206 and theremote network 210 primarily differ by the distances between their connected devices. Compared to theoriginal computing device 108 and thecaching computing device 104 connected through theremote network 210, theclient computing device 102 is physically closer to thecaching device 104 since they are connected through thelocal network 206. - Preferably, the cached portion of the application program cached at and executed by the
caching computing device 104 for theclient computing device 102 runs faster from thedevice 104 than any non-cached portion executed by theoriginal computing device 108. This can be for any number of reasons: First, thecaching computing device 104 may not have to execute the application program for as many clients as theoriginal computing device 108 does. Second, thelocal network 206 may be a faster network than theremote network 210. Moreover, thelocal network 206 may be less congested than theremote network 210. However, any portion of the application program cached and executed by theclient computing device 102 itself may run faster than if it is cached at and executed by thecaching computing device 104 or if it is executed by theoriginal computing device 108. - Referring back to
FIG. 1 , thefirst network 106 and thesecond network 110 may be the same network.FIG. 3 shows a diagram 300 of an embodiment in which thenetworks FIG. 1 are thesame network 308. For example, thenetwork 308 may include or be the Internet. As denoted by the curveddistance indication arrow 304, theoriginal computing device 108 is located physically farther away from theclient computing device 102 than thecaching computing device 104 is. For example, theclient computing device 102 may be located in Seattle, thecaching computing device 104 in Chicago, and theoriginal computing device 108 in London. As a result, the cached portion of the application program executed by thecaching computing device 104 for theclient computing device 102 generally runs faster than the portion executed by theoriginal computing device 108. Any portion cached and executed by theclient computing device 102 itself may runs faster still. - As has been described by reference to
FIGS. 1, 2 and 3, the invention relates to caching all or part of an application program by aclient computing device 102 and/or acaching computing device 104. Thedevice 104 executes its cached portion of the program for thedevice 102, and thedevice 102 executes its cached portion for itself. The application program may be partitioned into different parts, where each part is executed for theclient computing device 102 by either thedevice - A subsequent section of the detailed description describes how an application program originally meant for execution by an
original computing device 108 for aclient computing device 102 is instead executed by thedevice 102 or acaching computing device 104. Another section describes in detail how a program is downloaded from theoriginal computing device 108 and installed by thecaching computing device 104 or theclient computing device 102. An example computing device that can implement any of thedevices - Execution of a Cacheable Program by a Caching or a Client Computing Device
-
FIG. 4 is a diagram showing an embodiment of thecaching computing device 104 ofFIG. 1 in more detail. Thecaching computing device 104 is communicatively connected to the client computing device, as indicated by theline 402, and to the original computing device, as indicated by theline 404. Thecaching computing device 104 includes afirst component 406, asecond component 408, and cachedapplications 410. Thefirst component 406 and thesecond component 408 can be referred to as a plug-in and a service, respectively. They can be implemented within a single component. A component as used in this application refers to one or more sections of computer instructions, computer program modules, computer programs, and software objects. - The
first component 406 intercepts requests from the client computing device that are directed to application programs. Thefirst component 406 determines whether a given request relates to a part of an application that is cached in the cachedapplications 410. If so, thecomponent 406 redirects the request to the relevant application within the cachedapplications 410. Execution thus occurs at thecaching computing device 104, and not at the original computing device. If a given request does not relate to a part of an application that is cached in the cachedapplications 410, then thecomponent 406 passes the request through to the original computing device. -
FIG. 5 is a diagram that illustrates how in one embodiment adevice 500 particularly intercepts, redirects, and passes through application program requests. Thedevice 500 can be thecaching computing device 104 ofFIGS. 1 and 4 . Theapplication protocol handler 502 of thedevice 500 intercepts application program requests. A protocol specifies the form of the requests. A request may be in the form “rapp://www.aspco.com/program/directory/request.ext.” The indicator “rapp:” is used to specify that the request relates to a particular protocol, such as a “remote application program protocol.” The domain name “www.aspco.com” specifies a resource location, such as on the Internet. The indicators “program/” and “directory/” specify particular directories at this location, where “program/” is specifically used to identify the program that is being accessed. The request is made to a file at this location, as indicated by “request.ext”. - The
application protocol handler 502 examines all network traffic from the client computing device. If an item of traffic is preceded by the indicator “rapp:”, then thehandler 502 further determines whether the program specified by the request relates to a program that has been cached on thedevice 500. If it does not, then thehandler 502 passes the request through, as indicated by thearrow 503. Otherwise, thehandler 502 passes the request to the localname resolution handler 504. - The local
name resolution handler 504 redirects the application program request to the appropriate cached application. Thehandler 504 modifies the request to point to a particular handler for the program, from thelocal application handlers local application handler 506 b corresponds to the application indicated in this request, then thehandler 504 modifies the request to point to thelocal application handler 506 b. Thelocal application handler 506 b may be identified by “c:/wordprocessing/”. “c:” refers to a physical location within thedevice 500, such as a hard disk drive, and “wordprocessing/” refers to a directory at this physical location. Thehandler 504 modifies the request to “c:/wordprocessing/request.ext”, and thehandler 506 b handles the request for the cached application. - As has been described, an entire application may not have to be cached. Rather, only one or more parts of the application may be cached. In this situation, each application part may have its own local application handler within
handlers device 500. A given application program may comprise only one component, or a number of components. Where only one component makes up an application program, either the entire program or none of the program can be cached. Where a number of components make up an application program, any of the components can be cached. - Referring back to
FIG. 4 , preferably, the client computing device has no knowledge that execution may occur at thecaching computing device 104 instead of at the original computing device. The redirection and caching process performed by thecaching computing device 104 is preferably transparent to the client computing device. This means that the client computing device does not have to be reconfigured to afford execution by thecaching computing device 104. - The
second component 408 determines whether or not application programs that have not been cached in the cachedapplications 410 should be downloaded and installed on thecaching computing device 104. Thecomponent 408 constantly tracks client usage of application programs that are executed by the original computing device. Thecomponent 408 periodically assesses whether usage by the client computing device is sufficient to justify caching the application program for execution by thecaching computing device 104. Thecomponent 408 may download and install part or all of the program into the cachedapplications 410. Any criteria may be used to determine whether a program should be cached by thecaching computing device 104. - The client computing device may similarly cache and execute cached application programs or portions thereof.
FIG. 6 is a diagram showing an embodiment of theclient computing device 102 ofFIG. 1 in more detail. Theclient computing device 102 is communicatively connected to the caching and/or the original computing device, as indicated by theline 604. Like thecaching computing device 104 ofFIG. 4 , theclient computing device 102 ofFIG. 6 includes afirst component 606, asecond component 608, and cached applications 610. The first and thesecond components - The
first component 606 intercepts internal requests from theclient computing device 102 that are directed to application programs. Thefirst component 606 determines whether a given request relates to a part of an application that is cached in in the cached applications 610. If so, thecomponent 606 redirects the request to the part of the relevant application within the cached applications 610. Execution thus occurs at theclient computing device 102, and not at either the original or the caching computing device. If a given request does not relate to a part of an application that is cached in the cached applications 610, then thecomponent 606 passes the request through to the caching or the original computing device. Theclient computing device 102 can also intercept, redirect, and pass through application program requests as has been described by reference to FIG. where thedevice 500 ofFIG. 5 can be thedevice 102. - Still referring to
FIG. 6 , thesecond component 608 determines whether application programs that have not been cached in the cached applications 610 should be downloaded and installed on theclient computing device 102. Preferably, thecomponent 608 monitors usage of application programs by theclient computing device 102 that are executed for thedevice 102 by either the original or the caching computing device. Thecomponent 608 periodically assesses whether usage is sufficient to justify caching part or all of an application program for execution by theclient computing device 102. A criteria may be used to make this determination. When it is determined that an application program or a portion thereof should be cached at theclient computing device 102, thecomponent 608 downloads and installs the program or a portion thereof into the cached applications 610. -
FIG. 7 is a flowchart of amethod 700 summarizing how the client, caching, and original computing devices handle an application program request. The application program is initially installed only on the original computing device. Part or all of the program may subsequently be cached by the client computing device and/or the caching computing device. As indicated by the dottedlines method 700 are performed by the client computing device, some parts are performed by the caching computing device, and some parts by the original computing device. In particular, 706, 708, 710, and 712 are performed by the client computing device, 714, 716, 718, and 720 are performed by the caching computing device, and 722 by the original computing device. - In 706, the client computing device intercepts an internally generated request to an application program. In 708, the client computing device determines whether the request relates to a part of an application program that has been cached by the client device. If so, then the request is redirected in 710 so that the request is handled by the client computing device. The part of the application program to which the request relates is executed by the client computing device. If the request does not relate to a cached application, then the client computing device passes through the request in 712.
- In 714, the caching computing device intercepts the request passed through by the client computing device in 712. The caching computing device in 716 determines whether or not the request relates to a part of an application that has been cached by the caching device. If so, then the request is redirected in 718 so that the request is handled by the caching computing device. The part of the application program to which the request relates is executed by the caching computing device for the client computing device. If the request does not relate to a cached application part, then the caching computing device passes through the request in 720. The original computing device receives the request in 722, and handles the request. The part of the application program to which the request relates is executed by the original device for the client device.
-
FIG. 8 is a flowchart of amethod 800 summarizing how to determine whether part or all of an application program should be cached. The caching computing device can perform themethod 800 to determine whether it should cache at least a portion of the program. Likewise, the client computing device may perform themethod 800. In 802, the method tracks application program usage. Preferably, usage tracking is continuously performed. Periodically, the method determines in 804 whether at least part of an application program should be cached, based on a criteria. If not, then the method ends in 808. Otherwise, in 806, the method caches at least part of the program. The next section of the detailed description describes how a cacheable application program can be cached. - Caching (Downloading and Installing) a Cacheable Application Program
-
FIG. 9 is a flowchart of amethod 900 showing how one embodiment downloads and installs a cacheable application program. Themethod 900 is performed by thesecond component 408 of thecaching computing device 104 ofFIG. 4 , or thesecond component 608 of theclient computing device 102 ofFIG. 6 . The components perform themethod 900 after they have determined that an application program should be cached. The caching process of themethod 900 may fail at any point within the process. If this occurs, then themethod 900 exits without having successfully cached the application program, which is not specifically called out inFIG. 9 . - The description in this section focuses on downloading and installing an entire application program, which has not been partitioned into separate application program components. The description is also applicable to caching a component of an application program, by performing the
method 900 relative to such component, instead of to an entire application program. A cacheable application program or a component thereof is one that can be downloaded and installed as described in this section. - In 902, the method retrieves a pre-installation file for an application program from its original remote location at the original computing device. The pre-installation file is also referred to as a manifest. The manifest includes configuration and other information necessary for the program to be successfully cached. At a minimum, the manifest references the installation file(s) for the program that must be download and installed. Preferably, the manifest also references the amount of local storage space the application will occupy, and optionally the platform on which the application is intended to run. The manifest may also contain descriptive information such as the name of the application, the version of the application, a brief description of the application, and other information.
- In 904, the method determines whether or not the application program is installable on the computing device performing the method. This primarily involves two checks. First, the method verifies that the amount of available local storage space is sufficient for the program to be installed. The available local storage space may be the free space available on the hard disk drive of the computing device. Second, the method verifies that the computing device is compatible with the platform on which the application program is intended to be installed. The platform of the manifest may indicate the minimum version of an operating system on which the program can run. If the method determines that the application is not installable, then it proceeds to 906, where the method exits without having installed the application program.
- If the application program is installable, then the method proceeds to 908, where it downloads the installation file(s) specified by the manifest. In 909, the method installs the program on the device running the method by utilizing the installation file (s). The installation file(s) may be one or more cabinet (.CAB) files, which are installable on a computing device in a known manner. In 910, the method adds values regarding the installed application program in a central database. The central database is also referred to as a registry. Cached application programs are maintained in the registry, in which their original locations, such as on the original computing device, are mapped to their cached locations on the computing device. This enables redirection of program requests to the cached application programs. The registry may also maintain relevant installation information regarding the application programs, such as the time of installation and application usage information.
- For example, the method can add the following values to the registry for an installed application program:
- 1. The original location of the application program.
- 2. The system time at which the program was installed.
- 3. An application identifier, which can be automatically generated as a guaranteed unique identifier (GUID).
- 4. The physical location on the computing device where the application has been installed and where it can be executed from, which can be determined by a hash algorithm based on the application identifier.
- 5. The last time the application program was accessed, which defaults to the time of installation until the program is executed.
- Once the method has successfully cached the application program, it is finished in 912.
- Example Computing Device
-
FIG. 10 is a diagram of anexampling computing device 1000. Any of theclient computing device 102, thecaching computing device 104, and theoriginal computing device 108 ofFIG. 1 can be implemented as theexample device 1000. Theexample computing device 1000 can be, for example, a desktop computer, a laptop computer, or a personal digital assistant (PDA). The invention may be practiced with other computer system configurations as well, including multiprocessor systems, microprocessor-based or programmable consumer electronics, network computers, minicomputers, and mainframe computers. The invention may be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. - The
device 1000 includes one or more of the following components: processor(s) 1002,memory 1004,storage 1006, acommunications component 1008, input device (s) 1010, adisplay 1012, and output device(s) 1014. For a particular instantiation of thedevice 1000, one or more of these components may not be present. For example, a PDA may not have any output device(s) 1014. The description of thedevice 1000 is to be used as an overview of the types of components that typically reside within such a device, and is not meant as a limiting or exhaustive description. - The processor(s) 1002 may include a single central-processing unit (CPU), or a plurality of processing units, commonly referred to as a parallel processing environment. The
memory 1004 may include read-only memory (ROM) and/or random-access memory (RAM). Thestorage 1006 may be any type of storage, such as fixed-media storage devices and removable-media storage devices. Examples of the former include hard disk drives, and flash or other non-volatile memory. Examples of the latter include tape drives, optical drives like CD-ROM drives, and floppy disk drives. The storage devices and their associated computer-readable media provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data. Any type of computer-readable media that can store data and that is accessible by a computer can be used. - The
device 1000 may operate in a network environment. Examples of networks include the Internet, intranets, extranets, local-area networks (LAN's), and wide-area networks (WAN's). Thedevice 1000 may include acommunications component 1008, which can be present in or attached to thedevice 1000. Thecomponent 1008 may be one or more of a network card, an Ethernet card, an analog modem, a cable modem, a digital subscriber loop (DSL) modem, and an Integrated Services Digital Network (ISDN) adapter. The input device(s) 1010 are the mechanisms by which a user provides input to thedevice 1000. Such device(s) 1010 can include keyboards, pointing devices, microphones, joysticks, game pads, and scanners. Thedisplay 1012 is how thedevice 1000 typically shows output to the user. Thedisplay 1012 can include cathode-ray tube (CRT) display devices and flat-panel display (FPD) display devices. Thedevice 1000 may provide output to the user via other output device(s) 1014. The output device(s) 1014 can include speakers, printers, and other types of devices. - The methods that have been described can be computer-implemented. A computer-implemented method is desirably realized at least in part as one or more programs running on a computer. The programs can be executed from a computer-readable medium such as a memory by a processor of a computer. The programs are desirably storable on a machine-readable medium, such as a floppy disk or a CD-ROM, for distribution, and installation and execution on another computer. The program or programs can be a part of a computer system, a computer, or a computing device.
- It is noted that, although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement that is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the present invention. Therefore, it is manifestly intended that this invention be limited only by the claims and equivalents thereof.
Claims (28)
1. A method comprising:
receiving a request for executing a component of an application program, wherein the request is received in a caching computing device from an intercepting component of a second computing device, wherein the intercepting component is capable of intercepting the request by the second computing device that is addressed to an original computing device and redirecting the request to the caching computing device;
determining whether or not the request relates to a cacheable application program component that has been previously cached;
directing the request to the cacheable application program component for execution by the caching computing device in response to a determination that the request relates to the component that has been cached; and,
otherwise, passing the request to a third computing device.
2. The method of claim 1 , wherein the cacheable application program component constitutes the only component of a cacheable application program, such that the cacheable application program is wholly cached by caching the cacheable application program component.
3. The method of claim 1 , wherein the previously cacheable application program component was previously cached by:
downloading one or more installation files for the cacheable application program component from the original computing device; and,
installing the cacheable application program component onto the caching computing device by utilizing the one or more installation files.
4. (canceled)
5. The method of claim 1 , wherein the third computing device is the original computing device, and the method further comprising:
receiving the request by the original computing device, as has been passed by the caching computing device; and,
executing the application program component by the original computing device for the client computing device.
6-7. (canceled)
8. The method of claim 1 , wherein the steps of receiving, determining, directing and passing are performed by a client computing device, and directing the application program component request to the cacheable application program component that has been cached comprises executing the application program component by the client computing device for itself.
9. The method of claim 8 , wherein the third computing device is the original computing device, and the method further comprising:
receiving the request by the original computing device; and,
executing the application program component by the original computing device for the client computing device.
10-14. (canceled)
15. A machine-readable medium having instructions stored thereon for execution by a processor of a computing device to perform the method of claim 1 .
16-27. (canceled)
28. A computing device comprising:
a cacheable application program component of an application program that has been cached from an original computing device; and,
a redirection component configured to intercept requests for an application program component directed toward the original computing device and to direct any of the requests that relate to the application program component that has been cached to the application program component that has been cached.
29. The device of claim 28 , wherein the cacheable application program component constitutes the only component of a cacheable application program, such that the cacheable application program is wholly cached.
30. The device of claim 28 , wherein the device is a client computing device.
31. The device of claim 28 , wherein the device is a caching computing device.
32. The device of claim 28 , wherein the redirection component is further configured to otherwise pass the application program component requests that are irrelevant to the application program that has been cached to another computing device.
33-36. (canceled)
37. The device of claim 28 , wherein the the application program component is cached by downloading one or more installation files from the original computing device.
38-40. (canceled)
41. A system comprising:
an original computing device originally having one or more application program components installed thereon; and,
a caching computing device to cache at least one cacheable application program component from the original computing device and execute the at least one component for a client computing device in response to an application program component request originally directed to the original computing device, wherein the caching computing device is communicatively connected to the client computing device through a network.
42. The system of claim 41 , wherein any of the at least one application program components cached by the caching computing device constitute the only component of a cacheable application program, such that the cacheable application program is wholly cached by the caching computing device caching the cacheable application program component.
43. The system of claim 41 , wherein the client computing device is further configured to cache at least one cacheable application program component from the original computing device and execute the at least one component for itself.
44. (canceled)
45. The system of claim 41 , wherein the original computing device is also communicatively connected to the network.
46. The system of claim 41 , wherein the original computing device is communicatively connected to a second network, the caching computing device also communicatively connected to the second network.
47. The method of claim 1 further comprising:
receiving and caching, at the caching computing device, the application program or the component thereof from the third computing device, wherein the third computing device is the original computing device; and
in response to a request to execute the cached application program or the cached component, executing, at the caching computing device, the application program or the component thereof
wherein the request is received from an internal intercepting component capable of intercepting and redirecting the request.
48. (canceled)
49. The system of claim 41 further comprising:
a client computing device communicatively connected to the network, wherein the client computing device includes an internal intercepting component capable of intercepting and redirecting the application program component request.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/186,274 US20050273766A1 (en) | 2000-07-11 | 2005-07-21 | Application program caching |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US21760200P | 2000-07-11 | 2000-07-11 | |
US09/681,844 US6941351B2 (en) | 2000-07-11 | 2001-06-15 | Application program caching |
US11/186,274 US20050273766A1 (en) | 2000-07-11 | 2005-07-21 | Application program caching |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/681,844 Continuation US6941351B2 (en) | 2000-07-11 | 2001-06-15 | Application program caching |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050273766A1 true US20050273766A1 (en) | 2005-12-08 |
Family
ID=26912076
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/681,844 Expired - Lifetime US6941351B2 (en) | 2000-07-11 | 2001-06-15 | Application program caching |
US11/186,274 Abandoned US20050273766A1 (en) | 2000-07-11 | 2005-07-21 | Application program caching |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/681,844 Expired - Lifetime US6941351B2 (en) | 2000-07-11 | 2001-06-15 | Application program caching |
Country Status (3)
Country | Link |
---|---|
US (2) | US6941351B2 (en) |
EP (1) | EP1204025B1 (en) |
JP (2) | JP4290909B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070168987A1 (en) * | 2003-12-30 | 2007-07-19 | Eric Vetillard | Method for determining operational characteristics of a program |
US20120191803A1 (en) * | 2011-01-25 | 2012-07-26 | Microsoft Corporation | Decommissioning factored code |
CN105608147A (en) * | 2015-12-17 | 2016-05-25 | 无锡天脉聚源传媒科技有限公司 | Method and device for hiding original addresses of pictures |
US10277688B2 (en) | 2017-01-04 | 2019-04-30 | Microsoft Technology Licensing, Llc | Automatic installation activation selection for hosted services |
Families Citing this family (80)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6453334B1 (en) * | 1997-06-16 | 2002-09-17 | Streamtheory, Inc. | Method and apparatus to allow remotely located computer programs and/or data to be accessed on a local computer in a secure, time-limited manner, with persistent caching |
US7103650B1 (en) * | 2000-09-26 | 2006-09-05 | Microsoft Corporation | Client computer configuration based on server computer update |
US8799463B1 (en) | 2000-10-19 | 2014-08-05 | Ariba, Inc. | Method and apparatus for processing information related to interactive web sites |
US7062567B2 (en) | 2000-11-06 | 2006-06-13 | Endeavors Technology, Inc. | Intelligent network streaming and execution system for conventionally coded applications |
US8831995B2 (en) * | 2000-11-06 | 2014-09-09 | Numecent Holdings, Inc. | Optimized server for streamed applications |
US6996537B2 (en) | 2001-08-13 | 2006-02-07 | Qualcomm Incorporated | System and method for providing subscribed applications on wireless devices over a wireless network |
JP2003177992A (en) * | 2001-12-10 | 2003-06-27 | Seiko Epson Corp | Differential communication system, differential communication equipment, differential communication program and differential communication method |
EP1324217A1 (en) * | 2001-12-18 | 2003-07-02 | Hewlett-Packard Company, A Delaware Corporation | Process and cache system for providing an electronic service through a telecommunication network |
AU2003209194A1 (en) | 2002-01-08 | 2003-07-24 | Seven Networks, Inc. | Secure transport for mobile communication network |
US7899879B2 (en) | 2002-09-06 | 2011-03-01 | Oracle International Corporation | Method and apparatus for a report cache in a near real-time business intelligence system |
US7912899B2 (en) | 2002-09-06 | 2011-03-22 | Oracle International Corporation | Method for selectively sending a notification to an instant messaging device |
US8165993B2 (en) | 2002-09-06 | 2012-04-24 | Oracle International Corporation | Business intelligence system with interface that provides for immediate user action |
US7945846B2 (en) | 2002-09-06 | 2011-05-17 | Oracle International Corporation | Application-specific personalization for data display |
US7941542B2 (en) * | 2002-09-06 | 2011-05-10 | Oracle International Corporation | Methods and apparatus for maintaining application execution over an intermittent network connection |
US8255454B2 (en) | 2002-09-06 | 2012-08-28 | Oracle International Corporation | Method and apparatus for a multiplexed active data window in a near real-time business intelligence system |
US7412481B2 (en) | 2002-09-16 | 2008-08-12 | Oracle International Corporation | Method and apparatus for distributed rule evaluation in a near real-time business intelligence system |
US7401158B2 (en) | 2002-09-16 | 2008-07-15 | Oracle International Corporation | Apparatus and method for instant messaging collaboration |
US9232077B2 (en) * | 2003-03-12 | 2016-01-05 | Qualcomm Incorporated | Automatic subscription system for applications and services provided to wireless devices |
US7904823B2 (en) | 2003-03-17 | 2011-03-08 | Oracle International Corporation | Transparent windows methods and apparatus therefor |
US10043170B2 (en) | 2004-01-21 | 2018-08-07 | Qualcomm Incorporated | Application-based value billing in a wireless subscriber network |
US8812613B2 (en) | 2004-06-03 | 2014-08-19 | Maxsp Corporation | Virtual application manager |
US9357031B2 (en) * | 2004-06-03 | 2016-05-31 | Microsoft Technology Licensing, Llc | Applications as a service |
US7664834B2 (en) * | 2004-07-09 | 2010-02-16 | Maxsp Corporation | Distributed operating system management |
US7577949B2 (en) * | 2005-01-20 | 2009-08-18 | Microsoft Corporation | Installation source management |
US8234238B2 (en) * | 2005-03-04 | 2012-07-31 | Maxsp Corporation | Computer hardware and software diagnostic and report system |
US8589323B2 (en) | 2005-03-04 | 2013-11-19 | Maxsp Corporation | Computer hardware and software diagnostic and report system incorporating an expert system and agents |
US8024523B2 (en) | 2007-11-07 | 2011-09-20 | Endeavors Technologies, Inc. | Opportunistic block transmission with time constraints |
US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
WO2006136660A1 (en) | 2005-06-21 | 2006-12-28 | Seven Networks International Oy | Maintaining an ip connection in a mobile network |
US7941604B2 (en) * | 2006-02-01 | 2011-05-10 | Infineon Technologies Ag | Distributed memory usage for a system having multiple integrated circuits each including processors |
US8898319B2 (en) | 2006-05-24 | 2014-11-25 | Maxsp Corporation | Applications and services as a bundle |
US8811396B2 (en) | 2006-05-24 | 2014-08-19 | Maxsp Corporation | System for and method of securing a network utilizing credentials |
US20080077622A1 (en) * | 2006-09-22 | 2008-03-27 | Keith Robert O | Method of and apparatus for managing data utilizing configurable policies and schedules |
US7840514B2 (en) * | 2006-09-22 | 2010-11-23 | Maxsp Corporation | Secure virtual private network utilizing a diagnostics policy and diagnostics engine to establish a secure network connection |
US9317506B2 (en) * | 2006-09-22 | 2016-04-19 | Microsoft Technology Licensing, Llc | Accelerated data transfer using common prior data segments |
US8423821B1 (en) | 2006-12-21 | 2013-04-16 | Maxsp Corporation | Virtual recovery server |
US7844686B1 (en) | 2006-12-21 | 2010-11-30 | Maxsp Corporation | Warm standby appliance |
US8805425B2 (en) | 2007-06-01 | 2014-08-12 | Seven Networks, Inc. | Integrated messaging |
US8645515B2 (en) | 2007-10-26 | 2014-02-04 | Maxsp Corporation | Environment manager |
US8175418B1 (en) | 2007-10-26 | 2012-05-08 | Maxsp Corporation | Method of and system for enhanced data storage |
US8307239B1 (en) | 2007-10-26 | 2012-11-06 | Maxsp Corporation | Disaster recovery appliance |
US8892738B2 (en) | 2007-11-07 | 2014-11-18 | Numecent Holdings, Inc. | Deriving component statistics for a stream enabled application |
US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
US20090193338A1 (en) | 2008-01-28 | 2009-07-30 | Trevor Fiatal | Reducing network and battery consumption during content delivery and playback |
US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
CN102135892B (en) * | 2010-01-22 | 2015-03-04 | 广州华多网络科技有限公司 | Application program running method, device and system |
JP5567906B2 (en) | 2010-06-04 | 2014-08-06 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Apparatus and method for supporting screen reproduction |
PL3407673T3 (en) | 2010-07-26 | 2020-05-18 | Seven Networks, Llc | Mobile network traffic coordination across multiple applications |
US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
US20150195340A1 (en) * | 2010-09-30 | 2015-07-09 | Google Inc. | Determining if an Application is Cached |
US20120096048A1 (en) * | 2010-10-19 | 2012-04-19 | Microsoft Corporation | Personalized Object Dimension |
WO2012060995A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
WO2012071384A2 (en) | 2010-11-22 | 2012-05-31 | Michael Luna | Optimization of resource polling intervals to satisfy mobile device requests |
GB2501416B (en) | 2011-01-07 | 2018-03-21 | Seven Networks Llc | System and method for reduction of mobile network traffic used for domain name system (DNS) queries |
GB2517815A (en) | 2011-04-19 | 2015-03-04 | Seven Networks Inc | Shared resource and virtual resource management in a networked environment |
GB2504037B (en) | 2011-04-27 | 2014-12-24 | Seven Networks Inc | Mobile device which offloads requests made by a mobile application to a remote entity for conservation of mobile device and network resources |
US8621075B2 (en) | 2011-04-27 | 2013-12-31 | Seven Metworks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
EP2702524B1 (en) * | 2011-04-27 | 2017-10-04 | Seven Networks, LLC | Detection and filtering of malware based on traffic observations made in a distributed mobile traffic management system |
WO2013015995A1 (en) | 2011-07-27 | 2013-01-31 | Seven Networks, Inc. | Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network |
US8934414B2 (en) | 2011-12-06 | 2015-01-13 | Seven Networks, Inc. | Cellular or WiFi mobile traffic optimization based on public or private network destination |
WO2013086225A1 (en) | 2011-12-06 | 2013-06-13 | Seven Networks, Inc. | A mobile device and method to utilize the failover mechanisms for fault tolerance provided for mobile traffic management and network/device resource conservation |
WO2013086447A1 (en) | 2011-12-07 | 2013-06-13 | Seven Networks, Inc. | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
EP2788889A4 (en) | 2011-12-07 | 2015-08-12 | Seven Networks Inc | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
US20130159511A1 (en) | 2011-12-14 | 2013-06-20 | Seven Networks, Inc. | System and method for generating a report to a network operator by distributing aggregation of data |
WO2013103988A1 (en) | 2012-01-05 | 2013-07-11 | Seven Networks, Inc. | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
EP2645231A3 (en) * | 2012-03-29 | 2014-03-05 | Samsung Electronics Co., Ltd. | User terminal apparatus, method of controlling user terminal apparatus, image forming apparatus, and method of controlling image forming apparatus |
US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
US20130268656A1 (en) | 2012-04-10 | 2013-10-10 | Seven Networks, Inc. | Intelligent customer service/call center services enhanced using real-time and historical mobile application and traffic-related statistics collected by a distributed caching system in a mobile network |
US8775631B2 (en) | 2012-07-13 | 2014-07-08 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
US20140177497A1 (en) | 2012-12-20 | 2014-06-26 | Seven Networks, Inc. | Management of mobile device radio state promotion and demotion |
US9271238B2 (en) | 2013-01-23 | 2016-02-23 | Seven Networks, Llc | Application or context aware fast dormancy |
US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
US8750123B1 (en) | 2013-03-11 | 2014-06-10 | Seven Networks, Inc. | Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network |
US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
US10027753B2 (en) * | 2013-10-15 | 2018-07-17 | Microsoft Technology Licensing, Llc | Cloud service hosting on client device |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5859969A (en) * | 1995-01-10 | 1999-01-12 | Fujitsu Limited | Remote installation system and method |
US5859971A (en) * | 1996-02-15 | 1999-01-12 | International Business Machines Corp. | Differencing client/server communication system for use with CGI forms |
US5919247A (en) * | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
US6065043A (en) * | 1996-03-14 | 2000-05-16 | Domenikos; Steven D. | Systems and methods for executing application programs from a memory device linked to a server |
US6073129A (en) * | 1997-12-29 | 2000-06-06 | Bull Hn Information Systems Inc. | Method and apparatus for improving the performance of a database management system through a central cache mechanism |
US6205481B1 (en) * | 1998-03-17 | 2001-03-20 | Infolibria, Inc. | Protocol for distributing fresh content among networked cache servers |
US20010034736A1 (en) * | 1998-07-22 | 2001-10-25 | Dan Eylon | Method and system for executing network streamed application |
US6360366B1 (en) * | 1996-09-05 | 2002-03-19 | Managesoft Corporation | Systems and methods for automatic application version upgrading and maintenance |
US6430570B1 (en) * | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java application manager for embedded device |
US6430564B1 (en) * | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java data manager for embedded device |
US6442546B1 (en) * | 1998-12-30 | 2002-08-27 | At&T Corp. | Messaging system with application-defined states |
US20020138640A1 (en) * | 1998-07-22 | 2002-09-26 | Uri Raz | Apparatus and method for improving the delivery of software applications and associated data in web-based systems |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5771354A (en) * | 1993-11-04 | 1998-06-23 | Crawford; Christopher M. | Internet online backup system provides remote storage for customers using IDs and passwords which were interactively established when signing up for backup services |
CA2137488C (en) * | 1994-02-18 | 1998-09-29 | Richard I. Baum | Coexecuting method and means for performing parallel processing in conventional types of data processing systems |
DE19712127A1 (en) * | 1997-03-22 | 1998-10-22 | Lutz Dr Hagner | Buffer storage of program sections in computer network communication system |
JPH10334058A (en) * | 1997-05-27 | 1998-12-18 | Shikoku Nippon Denki Software Kk | On-line system and load dispersing system |
US6185598B1 (en) * | 1998-02-10 | 2001-02-06 | Digital Island, Inc. | Optimized network resource location |
US6128623A (en) | 1998-04-15 | 2000-10-03 | Inktomi Corporation | High performance object cache |
DE19829026A1 (en) | 1998-06-30 | 2000-01-05 | Alcatel Sa | Service providing system for telecommunications network |
JP2000172657A (en) * | 1998-12-08 | 2000-06-23 | Fujitsu Ltd | System and method for distributed processing, computer- readable recording medium with program for computer to execute the same method recorded therein, server device and client device |
-
2001
- 2001-06-15 US US09/681,844 patent/US6941351B2/en not_active Expired - Lifetime
- 2001-07-11 EP EP01116954.7A patent/EP1204025B1/en not_active Expired - Lifetime
- 2001-07-11 JP JP2001246809A patent/JP4290909B2/en not_active Expired - Lifetime
-
2005
- 2005-07-21 US US11/186,274 patent/US20050273766A1/en not_active Abandoned
- 2005-11-08 JP JP2005323748A patent/JP5072214B2/en not_active Expired - Lifetime
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5859969A (en) * | 1995-01-10 | 1999-01-12 | Fujitsu Limited | Remote installation system and method |
US5859971A (en) * | 1996-02-15 | 1999-01-12 | International Business Machines Corp. | Differencing client/server communication system for use with CGI forms |
US6065043A (en) * | 1996-03-14 | 2000-05-16 | Domenikos; Steven D. | Systems and methods for executing application programs from a memory device linked to a server |
US6115741A (en) * | 1996-03-14 | 2000-09-05 | Domenikos; Steven D. | Systems and methods for executing application programs from a memory device linked to a server |
US5919247A (en) * | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
US6360366B1 (en) * | 1996-09-05 | 2002-03-19 | Managesoft Corporation | Systems and methods for automatic application version upgrading and maintenance |
US6073129A (en) * | 1997-12-29 | 2000-06-06 | Bull Hn Information Systems Inc. | Method and apparatus for improving the performance of a database management system through a central cache mechanism |
US6205481B1 (en) * | 1998-03-17 | 2001-03-20 | Infolibria, Inc. | Protocol for distributing fresh content among networked cache servers |
US20010034736A1 (en) * | 1998-07-22 | 2001-10-25 | Dan Eylon | Method and system for executing network streamed application |
US20020138640A1 (en) * | 1998-07-22 | 2002-09-26 | Uri Raz | Apparatus and method for improving the delivery of software applications and associated data in web-based systems |
US6574618B2 (en) * | 1998-07-22 | 2003-06-03 | Appstream, Inc. | Method and system for executing network streamed application |
US6442546B1 (en) * | 1998-12-30 | 2002-08-27 | At&T Corp. | Messaging system with application-defined states |
US6430570B1 (en) * | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java application manager for embedded device |
US6430564B1 (en) * | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java data manager for embedded device |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070168987A1 (en) * | 2003-12-30 | 2007-07-19 | Eric Vetillard | Method for determining operational characteristics of a program |
US7827534B2 (en) * | 2003-12-30 | 2010-11-02 | Trusted Logic | Method for determining operational characteristics of a program |
US20120191803A1 (en) * | 2011-01-25 | 2012-07-26 | Microsoft Corporation | Decommissioning factored code |
CN105608147A (en) * | 2015-12-17 | 2016-05-25 | 无锡天脉聚源传媒科技有限公司 | Method and device for hiding original addresses of pictures |
US10277688B2 (en) | 2017-01-04 | 2019-04-30 | Microsoft Technology Licensing, Llc | Automatic installation activation selection for hosted services |
Also Published As
Publication number | Publication date |
---|---|
US20020035674A1 (en) | 2002-03-21 |
US6941351B2 (en) | 2005-09-06 |
EP1204025A3 (en) | 2006-06-14 |
JP2002182924A (en) | 2002-06-28 |
EP1204025A2 (en) | 2002-05-08 |
JP2006092569A (en) | 2006-04-06 |
JP5072214B2 (en) | 2012-11-14 |
EP1204025B1 (en) | 2018-09-19 |
JP4290909B2 (en) | 2009-07-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6941351B2 (en) | Application program caching | |
US6192398B1 (en) | Remote/shared browser cache | |
JP3978185B2 (en) | Fragment linking and fragment caching methods and systems | |
US7702800B2 (en) | Detecting and handling affinity breaks in web applications | |
US6877025B2 (en) | Integrated JSP and command cache for web applications with dynamic content | |
US20020116582A1 (en) | Batching of invalidations and new values in a web cache with dynamic content | |
US6480893B2 (en) | Web serving system | |
US7149809B2 (en) | System for reducing server loading during content delivery | |
US7178143B2 (en) | Multi-version hosting of application services | |
US9426244B2 (en) | Content delivery in a network | |
JP5193056B2 (en) | Method and system for maintaining up-to-date data of wireless devices | |
JP3481054B2 (en) | Gateway device, client computer and distributed file system connecting them | |
US20030187929A1 (en) | Multi-version hosting of application services | |
US20020194382A1 (en) | Method and system for efficient and automated version management of embedded objects in web documents | |
JP2005018773A (en) | General dependence model for invalidating cache entries | |
US6807606B2 (en) | Distributed execution coordination for web caching with dynamic content | |
US20120166572A1 (en) | Cache sharing among branch proxy servers via a master proxy server at a data center | |
US20020116583A1 (en) | Automatic invalidation dependency capture in a web cache with dynamic content | |
US20100325363A1 (en) | Hierarchical object caching based on object version | |
US20020111992A1 (en) | JSP composition in a cache for web applications with dynamic content | |
US6725265B1 (en) | Method and system for caching customized information | |
GB2347244A (en) | Processing class files | |
US6823360B2 (en) | Cofetching in a command cache | |
US20020112125A1 (en) | Command caching to improve network server performance | |
US20030046239A1 (en) | Content management and distribution |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034766/0001 Effective date: 20141014 |