CA2334004C - Backtracked incremental updating - Google Patents
Backtracked incremental updating Download PDFInfo
- Publication number
- CA2334004C CA2334004C CA002334004A CA2334004A CA2334004C CA 2334004 C CA2334004 C CA 2334004C CA 002334004 A CA002334004 A CA 002334004A CA 2334004 A CA2334004 A CA 2334004A CA 2334004 C CA2334004 C CA 2334004C
- Authority
- CA
- Canada
- Prior art keywords
- state
- final
- hub
- file
- incremental update
- 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.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99942—Manipulating data structure, e.g. compression, compaction, compilation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99954—Version management
Abstract
A computer readable file of an original state is updated to a final state. T he original state and the final state are both states within a sequence (100) o f states, which sequence (100) includes at least one hub state and one non-hub state. A first hub version, which corresponds to a hub state which is at lea st as early in the sequence as the original state, is stored locally. A hub incremental update (110) is retrieved (314) and used to update (316) the hub version to a second hub version, which second hub version corresponds to a h ub state which is at least as early in the sequence (100) as the final state. A final incremental update (112) is retrieved (320) and used with the file of the final hub versin to produce (322) a file of the final state. The files corresponding to both the second hub state and the final state are retained (324).
Description
wo ~~,z ~rn.~s99nzzzs BACKTR.ACKEp Il'JCREMENTA.>r UPDATING
REFFKENCE TO 1ZELATED APF'l.fC~TION
This application is related to co-pending, co~nonly assigned, LTtlited States Patent - No. 6,052,531, for "Mufti-Tiered Incremental Software Updating", issued on April 18, 20QU.
FIELD AF IIVVRTtTIOrI
o This invention pertains to the field o1' software updating. Mare specifically, this invention pertains to a system and method far using an archival version of a file to facilitate updating.
F3ACKGROUNI? OF THI: I~1VF?NTION
Soiree computer software publishers update their software applications (computer m programs and data files associated with the programs) fre,auently. These updates Aiten add new features to the applications as well as remove existing bugs. Several methods are commonly used to update software applications. The simplest of these is to distribute one entire software application to replace an older one. This full update method is simple, but expensive and inconvenient. Typically the software is di~~tributed on same type of removable 'o media, such as tloppy disks or CD-ROM's, which are costly to produce and distribute. The tame an end user trust wait far the removable medium to arrive and the time it takes For the software application to install itself on a catnputer system are inconvenient.
This inconvenience is compounded where updates. occur freque:ritly.
Because of the large size of many software applications it is generally not feasible to 's distribute full updates over computer networks, such as the Internet. When full updates of larger applications are distributed over a net'vrork, they often cause such high Ioads an servers that other users suffer slow-downs on the network, and the: servers have trouble meeting the demands.
In order to bypass marry of the problems associated with this type of software updating, so some software publishers distribute incremental upd2tes. 'These incremental updates do not contain entire software applications. but rathE~r they contain that information which is _ necessary to transform a particular version of a software application to a newer version. As used herein, the word "version" indicates a file or application of a specified state. Among the methods available to perforn~ such incremental software updating is binary patching, performed by programs such as RTPatch, published by Pocket Soft, Inc. A binary patcher changes those binary bits of a computer readable file which are different in a newer version. A
binary patcher needs, in addition to the old file, a data file which includes the differences between the two versions. Because most software updates involve changes to only a small portion of a software application, incremental update files are generally small. The smaller data files distributed for a binary patch incremental update are often less than I % of the size of ~o a full update. taking advantage of the large amount of redundancy in the two versions.
The use of incremental update methods allows for smaller updates which can be distributed by means which are not conducive to the distribution of full updates. such as distribution over the Internet. The smaller incremental updates also make distribution by floppy disk more feasible where a full update would have required many disks, and an m incremental update may require only one.
However, incremental update methods introduce another problem: an incremental update is specifically useful for updating only one particular version of a software application to another particular version. When updates occur frequently, as with virus protection software applications, end users may update from an arbitrarily old version to the newest zo version, skipping over several previously released versions. An incremental update for the newest version of a software application will generally update only from the most recent version, however. To update from an arbitrarily old version to the most recent version with incremental updates, a user often needs to acquire and apply a number of successive incremental updates.
2s One solution to this problem has been for software publishers to group a number of incremental update files together into one distribution. Each necessary incremental update is applied, one at a time, to update to the newest version. However, the number of incremental updates may be large. due to the fact that a grouping generally covers a large number of possible versions. The benefits of smaller distributed update tiles begin to disappear. as the 3o size of the grouped-together incremental updates grows. Lowering the number of update files available increases the amount of data the average user must acquire for an update, since the user will not need all of the incremental updates in a ~roupin~~. This method of updating _ applications can also be cumbersome. as a series of incremental updates needs to be selected from the group and applied to the software application one after another.
Another solution to the problem of incremental update version-specificity has been to create many unique incremental update files which each transform a different previous version s to the most current version. Then, only one incremental update is needed by any user.
However, where updates are very frequent, this scheme results in a large number of incremental update files to produce, store and maintain for users. In the case of publishers, such as virus-protection software publishers, who might update their applications as often as daily, this can quickly become untenable. The number of files which must be made available to with this scheme grows quickly, and makes the mirroring of incremental updates on a local server almost impossible. For example, in a case where a virus protection software publisher makes new virus definition files available daily, each year's worth of updates will require approximately 365 incremental update files.
One alternative to the methods described above is the use of "push"
technology, in Ts which a server maintains a database of what version each user has. The server then sends the necessary updates to each user, as they become available. This system requires "smart"
servers, however, to monitor user configurations, to determine what each user needs, and to send the appropriate update information. This results in a server-intensive system which can cause a drain on server resources comparable to that experienced in the full update scheme, ~o when many users are simultaneously requesting full updates. It is preferable to use a system which allows update files to be stored on a "dumb" server which simply provides specifically requested files.
What is needed is a system for updating software applications from an arbitrary first version to a newer version without requiring a large amount of information to be stored and 25 maintained by an update server, without requiring a user to acquire a large amount of data to perform each update, and without requiring the use of "smart" servers.
SUMMARY OF THE INVENTION
The present invention makes use of a "hub" version of a file to facilitate updating. The hub version is stored local to the version being updated. In one embodiment of the present o invention, at least one of a sequence (100) of versions of a computer readable file is designated a hub version. Hub incremental updates (110) are made available on a server (200) for updating previously published hub versions to the most recently published hub version. A
REFFKENCE TO 1ZELATED APF'l.fC~TION
This application is related to co-pending, co~nonly assigned, LTtlited States Patent - No. 6,052,531, for "Mufti-Tiered Incremental Software Updating", issued on April 18, 20QU.
FIELD AF IIVVRTtTIOrI
o This invention pertains to the field o1' software updating. Mare specifically, this invention pertains to a system and method far using an archival version of a file to facilitate updating.
F3ACKGROUNI? OF THI: I~1VF?NTION
Soiree computer software publishers update their software applications (computer m programs and data files associated with the programs) fre,auently. These updates Aiten add new features to the applications as well as remove existing bugs. Several methods are commonly used to update software applications. The simplest of these is to distribute one entire software application to replace an older one. This full update method is simple, but expensive and inconvenient. Typically the software is di~~tributed on same type of removable 'o media, such as tloppy disks or CD-ROM's, which are costly to produce and distribute. The tame an end user trust wait far the removable medium to arrive and the time it takes For the software application to install itself on a catnputer system are inconvenient.
This inconvenience is compounded where updates. occur freque:ritly.
Because of the large size of many software applications it is generally not feasible to 's distribute full updates over computer networks, such as the Internet. When full updates of larger applications are distributed over a net'vrork, they often cause such high Ioads an servers that other users suffer slow-downs on the network, and the: servers have trouble meeting the demands.
In order to bypass marry of the problems associated with this type of software updating, so some software publishers distribute incremental upd2tes. 'These incremental updates do not contain entire software applications. but rathE~r they contain that information which is _ necessary to transform a particular version of a software application to a newer version. As used herein, the word "version" indicates a file or application of a specified state. Among the methods available to perforn~ such incremental software updating is binary patching, performed by programs such as RTPatch, published by Pocket Soft, Inc. A binary patcher changes those binary bits of a computer readable file which are different in a newer version. A
binary patcher needs, in addition to the old file, a data file which includes the differences between the two versions. Because most software updates involve changes to only a small portion of a software application, incremental update files are generally small. The smaller data files distributed for a binary patch incremental update are often less than I % of the size of ~o a full update. taking advantage of the large amount of redundancy in the two versions.
The use of incremental update methods allows for smaller updates which can be distributed by means which are not conducive to the distribution of full updates. such as distribution over the Internet. The smaller incremental updates also make distribution by floppy disk more feasible where a full update would have required many disks, and an m incremental update may require only one.
However, incremental update methods introduce another problem: an incremental update is specifically useful for updating only one particular version of a software application to another particular version. When updates occur frequently, as with virus protection software applications, end users may update from an arbitrarily old version to the newest zo version, skipping over several previously released versions. An incremental update for the newest version of a software application will generally update only from the most recent version, however. To update from an arbitrarily old version to the most recent version with incremental updates, a user often needs to acquire and apply a number of successive incremental updates.
2s One solution to this problem has been for software publishers to group a number of incremental update files together into one distribution. Each necessary incremental update is applied, one at a time, to update to the newest version. However, the number of incremental updates may be large. due to the fact that a grouping generally covers a large number of possible versions. The benefits of smaller distributed update tiles begin to disappear. as the 3o size of the grouped-together incremental updates grows. Lowering the number of update files available increases the amount of data the average user must acquire for an update, since the user will not need all of the incremental updates in a ~roupin~~. This method of updating _ applications can also be cumbersome. as a series of incremental updates needs to be selected from the group and applied to the software application one after another.
Another solution to the problem of incremental update version-specificity has been to create many unique incremental update files which each transform a different previous version s to the most current version. Then, only one incremental update is needed by any user.
However, where updates are very frequent, this scheme results in a large number of incremental update files to produce, store and maintain for users. In the case of publishers, such as virus-protection software publishers, who might update their applications as often as daily, this can quickly become untenable. The number of files which must be made available to with this scheme grows quickly, and makes the mirroring of incremental updates on a local server almost impossible. For example, in a case where a virus protection software publisher makes new virus definition files available daily, each year's worth of updates will require approximately 365 incremental update files.
One alternative to the methods described above is the use of "push"
technology, in Ts which a server maintains a database of what version each user has. The server then sends the necessary updates to each user, as they become available. This system requires "smart"
servers, however, to monitor user configurations, to determine what each user needs, and to send the appropriate update information. This results in a server-intensive system which can cause a drain on server resources comparable to that experienced in the full update scheme, ~o when many users are simultaneously requesting full updates. It is preferable to use a system which allows update files to be stored on a "dumb" server which simply provides specifically requested files.
What is needed is a system for updating software applications from an arbitrary first version to a newer version without requiring a large amount of information to be stored and 25 maintained by an update server, without requiring a user to acquire a large amount of data to perform each update, and without requiring the use of "smart" servers.
SUMMARY OF THE INVENTION
The present invention makes use of a "hub" version of a file to facilitate updating. The hub version is stored local to the version being updated. In one embodiment of the present o invention, at least one of a sequence (100) of versions of a computer readable file is designated a hub version. Hub incremental updates (110) are made available on a server (200) for updating previously published hub versions to the most recently published hub version. A
- final incremental update ( I 12) is also made available on the server (200), for updating the most recently published hub version to the current version. A previously published hub version can be used with the two incremental updates (110. 112) to produce a file of the current version.
The first incremental update (110) is used (316) to produce the most recent hub version, and the second incremental update (112) is used (322) to produce the current version.
When such an update is earned out, an intermediate version ofthe file, the most recent hub version, is produced (316). The file of the most recent hub version is retained (324) locally subsequent to the current version being constructed (322). The current version is used as an active version (208), while the most recent hub version is an archive version (206). The to next time an update is carried out, the archive (206) version is used with just the two new incremental update files (110, 112) to update to the new current version. If there are few hubs, the number of incremental update patches which must be made available is small. For example, if a virus protection sottware publisher makes new virus definition files available daily, the publisher may designate as hubs those versions which coincide with the first of each 1s month. Over a year's worth of incremental updates can be stored on the publisher's server (200) in the form of thirteen hub incremental updates (110) and one final incremental update (112). Unlike the case in which large numbers of incremental updates are grouped together to lower the number of files to be maintained, each of the hub incremental updates (110) and the final incremental update (112) can be as small as any other incremental updates.
2o In another embodiment of the present invention, information about the differences between the active version (208) and the archive version (206) are stored locally instead of the full archive version (206). Before an update takes place, this information is used with the active version (208) of the file to construct the archive version (206). This constructed archive version (206) is then used as above to accomplish the update.
?s In yet another embodiment of the present invention, the only hub version in the sequence of versions is the initial version. This initial version is maintained locally at all times for update purposes. When an update to a new version of the file is to be performed, only a final incremental update (112) which constructs the current version from the initial version is required. In this way a publisher can make an update generally available to users of many 3o different versions by publishing a single final incremental update (112).
Each user, although possibly using an active version (208) which is newer than the initial version. has a Ioca1 copy of the initial version (206) available.
The first incremental update (110) is used (316) to produce the most recent hub version, and the second incremental update (112) is used (322) to produce the current version.
When such an update is earned out, an intermediate version ofthe file, the most recent hub version, is produced (316). The file of the most recent hub version is retained (324) locally subsequent to the current version being constructed (322). The current version is used as an active version (208), while the most recent hub version is an archive version (206). The to next time an update is carried out, the archive (206) version is used with just the two new incremental update files (110, 112) to update to the new current version. If there are few hubs, the number of incremental update patches which must be made available is small. For example, if a virus protection sottware publisher makes new virus definition files available daily, the publisher may designate as hubs those versions which coincide with the first of each 1s month. Over a year's worth of incremental updates can be stored on the publisher's server (200) in the form of thirteen hub incremental updates (110) and one final incremental update (112). Unlike the case in which large numbers of incremental updates are grouped together to lower the number of files to be maintained, each of the hub incremental updates (110) and the final incremental update (112) can be as small as any other incremental updates.
2o In another embodiment of the present invention, information about the differences between the active version (208) and the archive version (206) are stored locally instead of the full archive version (206). Before an update takes place, this information is used with the active version (208) of the file to construct the archive version (206). This constructed archive version (206) is then used as above to accomplish the update.
?s In yet another embodiment of the present invention, the only hub version in the sequence of versions is the initial version. This initial version is maintained locally at all times for update purposes. When an update to a new version of the file is to be performed, only a final incremental update (112) which constructs the current version from the initial version is required. In this way a publisher can make an update generally available to users of many 3o different versions by publishing a single final incremental update (112).
Each user, although possibly using an active version (208) which is newer than the initial version. has a Ioca1 copy of the initial version (206) available.
_ BRIEF DESCRIPTION OF THE DRA~"JIVC~S
Fig. 1 is an illustration of a sequence 100 of file versions and the incremental updates 110, 112 for transforming them.
Fig. ? is an illustration of one embodiment of the present invention.
Fig. 3 is a flowchart illustrating the operation of one embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Referring now to Fig. 1, a sequence 100 of states I.0-3.2 of a computer readable file is shown. Each numbered state corresponds to a later state of the file than states with lower To numerical designations. Those versions with numerical designations ending in ".0"
correspond to hub versions. In one embodiment, hub versions are major versions and non-hub versions are minor versions. The designation of hub versions does not need to be based on any such distinction, however. In the illustrative embodiment, the computer readable file is a virus definition file used by a virus detection program. As used herein, the terns computer readable file encompasses one or more associated files. A computer readable file can be an executable file, a graphics file, an audio file, a data file, a complete software application comprising files of different types, or any other type of computer readable file which can be accessed and updated by a computer.
In Fib. 1, two hub incremental updates 110 are each used to construct a hub version zo from an earlier hub version. One hub incremental update 110 connects state 1.0 to state 3.0, and the other connects state 2.0 to state 3Ø The hub incremental update 110 shown connecting states 1.0 and 3.0 is an incremental update file which is used to construct a version 3.0 file from a version 1.0 file. Final incremental update 112 is an incremental update file which can be used to construct the most recent version (in this case 3.2) from the most recent hub version (in this case 3.0).
Referring now to Fig. 2, local computer 204 includes two versions of the computer readable file. Active file 208 is the most recent version available on computer 204, and is used by a virus scanner program. Archive file 206 corresponds to a hub state 1.0 preceding, in sequence 100, the state 1.1 corresponding to active file 208. In an exemplary embodiment of o the present invention, archive file 206 is the latest hub version which is not later in sequence 100 than active file 208. When active file 208 is a hub version, redundancy is avoided by storing only one version of the file on computer 204, since both archive file 206 and active file 208 are the same Cle in that case. ~~rchive file 206, being an older version, is generally not used on computer 204, except in conjunction with updating.
Updater 210, a program local to computer 204, is used to update active file 208 and archive file 206. Provided with an incremental update, updater 210 can create an updated version from an older version. Incremental update files I 10 and 112, and updater 210, can be implemented using a conventional incremental update system, such as binary patching.
In other embodiments of the present invention, archive file 206 is stored on computer 204 in a compressed form. This compressed form can be any conventional form of file compression. In one embodiment, archive file 206 is stored on computer 204 in the form of a io file indicating the binary differences between uncompressed archive file 206 and active file 208. If archive file 206 is stored in compressed form, it is uncompressed prior to being used for updating.
A software publisher makes several hub incremental updates 110 and one final incremental update 112 available on server 200. Server 200 transmits an incremental update ~5 file to local computer 204 in response to a request for the file. Server 200 can be a file server on a local area network (LAN), a file server on a wide area network (WAN), an FTP (File Transfer Protocol) server, an HTTP (Hypertext Transfer Protocol) server, or an NNTP
(Network News Transfer Protocol) server. Additionally, server 200 can be a removable magnetic or optical storage medium, or any other type of storage device capable of supplying 2o computer readable files to local computer 204 in response to a request for such files. The minimal requirements for server 200 enable conventional. inexpensive dumb servers to be used.
The operation of an exemplary embodiment is described with reference to Fig.
3. First, active file 208 to be updated is selected 300 as the Original_State. Then, the most recent 25 version available on server 200 is identified 302 by updater 210 as the Final State. The most recent locally available hub version is designated 304 the Original_Hub. This is ordinarily archive file 206. Where active file 208 is a hub version, however, Original-Hub will be Original State. Next, the most recent hub version available on server 200 is identified 306 by updater 210 as the Final-Hub. Ordinarily, the Final Hub state will precede the Final_State in 3o the sequence of states. Where Final-State is a hub state, however, they will be the same.
A test is performed 312 by updater 210 to determine whether Original-_Hub and Final Hub correspond to the same state. If they do, no hub updating is necessary. Otherwise, _ hub updating is necessary, and a hub incremental update 110 is retrieved 314 from server 200.
The hub incremental update 110 retrieved is an incremental update for use in transforming a file of Original-Hub state to Final-Hub state. Hub incremental update 110 can be downloaded over a network, or it can be read from a removable medium, such as a magnetic or optical disk.
Hub incremental update 110 is used by updater 210 to transform 316 archive file 206 from the Original Hub state to the Final Hub state.
After producing a file of Final-Hub state on local computer 204, a test is performed 31$ by updater 210 to determine whether Final Hub is the same state as Final-State. If so, no further updating is necessary to obtain the Final_State version. Otherwise final incremental o update 112 is retrieved 320 from server 200. Final incremental update 112 is the incremental update which is used to transform a file from Final Hub state to Final State.
After being retrieved, final incremental update 112 is used by updater 210 to create 322 Final State from Final Hub. The Final Hub version is retained 324 on local computer 204 after Final-State has been produced. If the updating scheme used by updater 210 is one which replaces the file Is being updated with a new one, then it is necessary to create a copy of Final Hub prior to applying final incremental update 112 to it. When the updating is completed, the Final-Hub version is archive file 206, and the Final State version is active file 208.
For clarity, in the exemplary embodiment described above, the Final_State and the Final Hub state are explicitly identified by updater (210). In a preferred embodiment, each 2o hub incremental update 110 is packaged with final incremental update 112 on server 200. This package is identified as corresponding to the Original Hub state to which the included hub incremental update 110 applies. Rather than determining what the Final Hub and Final-State are, updater 210 requests the package identified as being for Original Hub state, extracts the included incremental updates, and applies them to Original Hub. If Original Hub is the same z~ as Final Hub, the package does not contain a hub incremental update 110, and if the Final Hub is the Final State, no final incremental update 112 is included. In this embodiment, updater 2I0 does not explicitly determine whether Original Hub is the same as Final Hub, or whether Final Hub is the same as Final State. For simplicity, only one file needs to be retrieved, and communication between updater 210 and server 200 is minimized.
3o Suitable methods for packaging the files together are known in the art, and include the Java Archive (JAR) platform-independent file format, available from Sun Microsystems.
By increasing the amount of information stored locally. the present invention permits updating from a small number of incremental updates retrieved from a dumb server without requiring that a large number of incremental update files are stored on the server. Such a system lends itself to mirroring, where the incremental update files necessary for an update are s stored on servers other than those controlled by the publisher. For example, a company can maintain locally the files necessary to support frequent updating of a particular application.
Employees of the company can access the files through a LAN in order to accomplish updating. This would be difficult with conventional systems. because either the company would need to maintain a very large number of files, or the amount of information sent over to the LAN to support updates would be large. The trade-off for the lower amount of information sent over the network and the lower amount of information stored on the update server is that a larger amount of information is stored on each user's local computer. This trade-off is generally acceptable. since mass storage costs are low and only one archival version of an application must be stored on each local computer.
~s The above description is included to illustrate the operation of exemplary embodiments and is not meant to limit the scope of the invention. The scope of the invention is to be limited only by the following claims. From the above description, many variations will be apparent to one skilled in the art that would be encompassed by the spirit and scope of the present invention.
2o What is claimed is:
Fig. 1 is an illustration of a sequence 100 of file versions and the incremental updates 110, 112 for transforming them.
Fig. ? is an illustration of one embodiment of the present invention.
Fig. 3 is a flowchart illustrating the operation of one embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Referring now to Fig. 1, a sequence 100 of states I.0-3.2 of a computer readable file is shown. Each numbered state corresponds to a later state of the file than states with lower To numerical designations. Those versions with numerical designations ending in ".0"
correspond to hub versions. In one embodiment, hub versions are major versions and non-hub versions are minor versions. The designation of hub versions does not need to be based on any such distinction, however. In the illustrative embodiment, the computer readable file is a virus definition file used by a virus detection program. As used herein, the terns computer readable file encompasses one or more associated files. A computer readable file can be an executable file, a graphics file, an audio file, a data file, a complete software application comprising files of different types, or any other type of computer readable file which can be accessed and updated by a computer.
In Fib. 1, two hub incremental updates 110 are each used to construct a hub version zo from an earlier hub version. One hub incremental update 110 connects state 1.0 to state 3.0, and the other connects state 2.0 to state 3Ø The hub incremental update 110 shown connecting states 1.0 and 3.0 is an incremental update file which is used to construct a version 3.0 file from a version 1.0 file. Final incremental update 112 is an incremental update file which can be used to construct the most recent version (in this case 3.2) from the most recent hub version (in this case 3.0).
Referring now to Fig. 2, local computer 204 includes two versions of the computer readable file. Active file 208 is the most recent version available on computer 204, and is used by a virus scanner program. Archive file 206 corresponds to a hub state 1.0 preceding, in sequence 100, the state 1.1 corresponding to active file 208. In an exemplary embodiment of o the present invention, archive file 206 is the latest hub version which is not later in sequence 100 than active file 208. When active file 208 is a hub version, redundancy is avoided by storing only one version of the file on computer 204, since both archive file 206 and active file 208 are the same Cle in that case. ~~rchive file 206, being an older version, is generally not used on computer 204, except in conjunction with updating.
Updater 210, a program local to computer 204, is used to update active file 208 and archive file 206. Provided with an incremental update, updater 210 can create an updated version from an older version. Incremental update files I 10 and 112, and updater 210, can be implemented using a conventional incremental update system, such as binary patching.
In other embodiments of the present invention, archive file 206 is stored on computer 204 in a compressed form. This compressed form can be any conventional form of file compression. In one embodiment, archive file 206 is stored on computer 204 in the form of a io file indicating the binary differences between uncompressed archive file 206 and active file 208. If archive file 206 is stored in compressed form, it is uncompressed prior to being used for updating.
A software publisher makes several hub incremental updates 110 and one final incremental update 112 available on server 200. Server 200 transmits an incremental update ~5 file to local computer 204 in response to a request for the file. Server 200 can be a file server on a local area network (LAN), a file server on a wide area network (WAN), an FTP (File Transfer Protocol) server, an HTTP (Hypertext Transfer Protocol) server, or an NNTP
(Network News Transfer Protocol) server. Additionally, server 200 can be a removable magnetic or optical storage medium, or any other type of storage device capable of supplying 2o computer readable files to local computer 204 in response to a request for such files. The minimal requirements for server 200 enable conventional. inexpensive dumb servers to be used.
The operation of an exemplary embodiment is described with reference to Fig.
3. First, active file 208 to be updated is selected 300 as the Original_State. Then, the most recent 25 version available on server 200 is identified 302 by updater 210 as the Final State. The most recent locally available hub version is designated 304 the Original_Hub. This is ordinarily archive file 206. Where active file 208 is a hub version, however, Original-Hub will be Original State. Next, the most recent hub version available on server 200 is identified 306 by updater 210 as the Final-Hub. Ordinarily, the Final Hub state will precede the Final_State in 3o the sequence of states. Where Final-State is a hub state, however, they will be the same.
A test is performed 312 by updater 210 to determine whether Original-_Hub and Final Hub correspond to the same state. If they do, no hub updating is necessary. Otherwise, _ hub updating is necessary, and a hub incremental update 110 is retrieved 314 from server 200.
The hub incremental update 110 retrieved is an incremental update for use in transforming a file of Original-Hub state to Final-Hub state. Hub incremental update 110 can be downloaded over a network, or it can be read from a removable medium, such as a magnetic or optical disk.
Hub incremental update 110 is used by updater 210 to transform 316 archive file 206 from the Original Hub state to the Final Hub state.
After producing a file of Final-Hub state on local computer 204, a test is performed 31$ by updater 210 to determine whether Final Hub is the same state as Final-State. If so, no further updating is necessary to obtain the Final_State version. Otherwise final incremental o update 112 is retrieved 320 from server 200. Final incremental update 112 is the incremental update which is used to transform a file from Final Hub state to Final State.
After being retrieved, final incremental update 112 is used by updater 210 to create 322 Final State from Final Hub. The Final Hub version is retained 324 on local computer 204 after Final-State has been produced. If the updating scheme used by updater 210 is one which replaces the file Is being updated with a new one, then it is necessary to create a copy of Final Hub prior to applying final incremental update 112 to it. When the updating is completed, the Final-Hub version is archive file 206, and the Final State version is active file 208.
For clarity, in the exemplary embodiment described above, the Final_State and the Final Hub state are explicitly identified by updater (210). In a preferred embodiment, each 2o hub incremental update 110 is packaged with final incremental update 112 on server 200. This package is identified as corresponding to the Original Hub state to which the included hub incremental update 110 applies. Rather than determining what the Final Hub and Final-State are, updater 210 requests the package identified as being for Original Hub state, extracts the included incremental updates, and applies them to Original Hub. If Original Hub is the same z~ as Final Hub, the package does not contain a hub incremental update 110, and if the Final Hub is the Final State, no final incremental update 112 is included. In this embodiment, updater 2I0 does not explicitly determine whether Original Hub is the same as Final Hub, or whether Final Hub is the same as Final State. For simplicity, only one file needs to be retrieved, and communication between updater 210 and server 200 is minimized.
3o Suitable methods for packaging the files together are known in the art, and include the Java Archive (JAR) platform-independent file format, available from Sun Microsystems.
By increasing the amount of information stored locally. the present invention permits updating from a small number of incremental updates retrieved from a dumb server without requiring that a large number of incremental update files are stored on the server. Such a system lends itself to mirroring, where the incremental update files necessary for an update are s stored on servers other than those controlled by the publisher. For example, a company can maintain locally the files necessary to support frequent updating of a particular application.
Employees of the company can access the files through a LAN in order to accomplish updating. This would be difficult with conventional systems. because either the company would need to maintain a very large number of files, or the amount of information sent over to the LAN to support updates would be large. The trade-off for the lower amount of information sent over the network and the lower amount of information stored on the update server is that a larger amount of information is stored on each user's local computer. This trade-off is generally acceptable. since mass storage costs are low and only one archival version of an application must be stored on each local computer.
~s The above description is included to illustrate the operation of exemplary embodiments and is not meant to limit the scope of the invention. The scope of the invention is to be limited only by the following claims. From the above description, many variations will be apparent to one skilled in the art that would be encompassed by the spirit and scope of the present invention.
2o What is claimed is:
Claims (24)
PROPERTY OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A method for facilitating updating of a computer readable file to a final state, the final state being a state within an ordered sequence of states associated with the file, the sequence including at least one hub state, the method comprising the steps of:
determining as a final hub state a hub state which is at least as early in the sequence as the final state;
for each hub state which is earlier in the sequence than the final hub state, making available a hub incremental update containing information about differences between that hub state and the final hub state; and responsive to the final hub state not being the final state, making available a final incremental update containing information about differences between the final hub state and the final state.
determining as a final hub state a hub state which is at least as early in the sequence as the final state;
for each hub state which is earlier in the sequence than the final hub state, making available a hub incremental update containing information about differences between that hub state and the final hub state; and responsive to the final hub state not being the final state, making available a final incremental update containing information about differences between the final hub state and the final state.
2. The method of claim 1, wherein the sequence includes at least one state which is not a hub state.
3. The method of claim 1, wherein the step of making available a final incremental update comprises, for each hub incremental update, making available a package including the hub incremental update and the final incremental update.
4. The method of claim 1, wherein the step of determining the final hub state comprises selecting the latest hub state which is not preceded in the sequence by the final state.
5. The method of claim 1, wherein the sequence of states is a temporal sequence, and each state in the sequence is associated with a position in time.
6. The method of claim 1, wherein the step of making available a hub incremental update comprises putting the hub incremental update on a server computer, and the step of making available a final incremental update comprises putting the final incremental update on the server computer.
7. The method of claim 1, wherein the step of making available a hub incremental update comprises putting the hub incremental update on a removable computer readable storage medium and the step of making available a final incremental update comprises putting the final incremental update on the removable computer readable storage medium.
8. A method for updating a computer readable file of an original state to a final state, the file of the original state residing on a local computer system, the original state and the final state being states within an ordered sequence of states associated with the file, the final state being later in the sequence than the original state, and the sequence including a final hub state which is not preceded in the sequence by the final state, the method comprising the steps of accessing from a local storage location a file of an original hub state, the original hub state being a hub state in the sequence which is not preceded in the sequence by the original state;
responsive to the original hub state not being the final hub state:
accessing a hub incremental update containing information about differences between the original hub state and the final hub state;
using the hub incremental update and the file of the original hub state to produce a file of the final hub state; and storing the file of the final hub state; and responsive to the final hub state not being the final state:
accessing a final incremental update containing information about differences between the final hub state and the final state;
using the final incremental update and the file of the final hub state to produce a file of the final state; and storing the file of the final state.
responsive to the original hub state not being the final hub state:
accessing a hub incremental update containing information about differences between the original hub state and the final hub state;
using the hub incremental update and the file of the original hub state to produce a file of the final hub state; and storing the file of the final hub state; and responsive to the final hub state not being the final state:
accessing a final incremental update containing information about differences between the final hub state and the final state;
using the final incremental update and the file of the final hub state to produce a file of the final state; and storing the file of the final state.
9. The method of claim 8, wherein the sequence includes at least one state which is not a hub state.
10. The method of claim 8, wherein the hub incremental update and the final incremental update are included in a package, and the sub-step of accessing the hub incremental update and the sub-step of accessing the final update are both performed by accessing the package.
11. The method of claim 8, wherein the local storage location is internal to the local computer system.
12. The method of claim 8, wherein the local storage location is a removable computer readable storage medium.
13. The method of claim 8, wherein the sub-step of accessing a hub incremental update comprises accessing the hub incremental update over a computer network, and the sub-step of accessing a final incremental update comprises accessing the final incremental update over the computer network.
14. The method of claim 8, wherein the original hub state is the latest hub state which is not preceded in the sequence by the original state.
15. The method of claim 8, wherein the final hub state is the latest hub state which is not preceded in the sequence by the final state.
16. The method of claim 8, wherein the sub-step of storing the file of the final hub state comprises replacing the file of the original hub state in the local storage location with the file of the final hub state.
17. The method of claim 8, wherein the sequence of states is a temporal sequence, and each state is associated with a position in time.
18. The method of claim 8, wherein the sub-step of storing the file of the final hub state comprises storing the file of the final hub state in a compressed form.
19. The method of claim 8, wherein the sub-step of storing the file of the final hub state comprises storing information which can be used with the file of the final state to produce a file of the final hub state.
20. The method of claim 8, wherein there is only one hub state in the sequence, the hub state not being preceded in the sequence by the original state.
21. A system for facilitating updating of a computer readable file to a final state, the file residing on a local computer, the final state being a state within an ordered sequence of states associated with the file, the sequence including a final hub state which is a hub state that is not preceded in the sequence by the final state, the system comprising:
for each hub state preceding the final hub state in the sequence, a hub incremental update containing information about differences between that hub state and the final hub state;
a final incremental update containing information about differences between the final hub state and the final state;
a server coupled to the local computer, which server has access to any hub incremental updates and the final incremental update, and which, in response to a request by the local computer for an incremental update, transmits the requested incremental update to the local computer.
for each hub state preceding the final hub state in the sequence, a hub incremental update containing information about differences between that hub state and the final hub state;
a final incremental update containing information about differences between the final hub state and the final state;
a server coupled to the local computer, which server has access to any hub incremental updates and the final incremental update, and which, in response to a request by the local computer for an incremental update, transmits the requested incremental update to the local computer.
22. The system of claim 21, wherein the server is coupled to the local computer by a computer network.
23. The system of claim 21, wherein the server is a removable computer readable storage medium.
24. A computer readable medium containing a computer program for updating a computer readable file of an original state to a final state, the file of the original state residing on a local computer system, the original state and the final state being states within an ordered sequence of states associated with the file, the final state being later in the sequence than the original state, the sequence including as a final hub state a hub state which is not preceded in the sequence by the final state, and the computer program, when executed by the local computer system, causing the local computer system to perform the steps of accessing from a local storage location a file of an original hub state, the original hub state being a hub state which is not preceded in the sequence by the original state;
responsive to the original hub state not being the final hub state:
accessing a hub incremental update containing information about differences between the original hub state and the final hub state;
using the hub incremental update and the file of the original hub state to produce a file of the final hub state; and storing the file of the final hub state; and responsive to the final hub state not being the final state:
accessing a final incremental update containing information about differences between the final hub state and the final state;
using the final incremental update and the file of the final hub state to produce a file of the final state; and storing the file of the final state.
responsive to the original hub state not being the final hub state:
accessing a hub incremental update containing information about differences between the original hub state and the final hub state;
using the hub incremental update and the file of the original hub state to produce a file of the final hub state; and storing the file of the final hub state; and responsive to the final hub state not being the final state:
accessing a final incremental update containing information about differences between the final hub state and the final state;
using the final incremental update and the file of the final hub state to produce a file of the final state; and storing the file of the final state.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US09/089,930 US6167407A (en) | 1998-06-03 | 1998-06-03 | Backtracked incremental updating |
| US09/089,930 | 1998-06-03 | ||
| PCT/US1999/012228 WO1999063432A2 (en) | 1998-06-03 | 1999-06-02 | Backtracked incremental updating |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2334004A1 CA2334004A1 (en) | 1999-12-09 |
| CA2334004C true CA2334004C (en) | 2002-04-09 |
Family
ID=22220272
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002334004A Expired - Fee Related CA2334004C (en) | 1998-06-03 | 1999-06-02 | Backtracked incremental updating |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US6167407A (en) |
| EP (1) | EP1082651B1 (en) |
| CA (1) | CA2334004C (en) |
| DE (1) | DE69905158T2 (en) |
| WO (1) | WO1999063432A2 (en) |
Families Citing this family (70)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6035423A (en) | 1997-12-31 | 2000-03-07 | Network Associates, Inc. | Method and system for providing automated updating and upgrading of antivirus applications using a computer network |
| US6158010A (en) * | 1998-10-28 | 2000-12-05 | Crosslogix, Inc. | System and method for maintaining security in a distributed computer network |
| US7673323B1 (en) * | 1998-10-28 | 2010-03-02 | Bea Systems, Inc. | System and method for maintaining security in a distributed computer network |
| US6484315B1 (en) * | 1999-02-01 | 2002-11-19 | Cisco Technology, Inc. | Method and system for dynamically distributing updates in a network |
| US6230199B1 (en) | 1999-10-29 | 2001-05-08 | Mcafee.Com, Inc. | Active marketing based on client computer configurations |
| JP3655152B2 (en) * | 1999-11-29 | 2005-06-02 | 富士通株式会社 | Software editing apparatus and storage medium |
| US6584475B1 (en) * | 1999-12-15 | 2003-06-24 | Oracle International Corporation | System for controlling database growth in a read-repeatable environment |
| US6820088B1 (en) * | 2000-04-10 | 2004-11-16 | Research In Motion Limited | System and method for synchronizing data records between multiple databases |
| US20040073617A1 (en) | 2000-06-19 | 2004-04-15 | Milliken Walter Clark | Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail |
| EP1168165A3 (en) * | 2000-06-30 | 2005-02-16 | International Business Machines Corporation | Device and method for updating code |
| KR100455566B1 (en) | 2000-06-30 | 2004-11-09 | 인터내셔널 비지네스 머신즈 코포레이션 | Device and method for updating code |
| US7051069B2 (en) | 2000-09-28 | 2006-05-23 | Bea Systems, Inc. | System for managing logical process flow in an online environment |
| US6965928B1 (en) | 2001-03-09 | 2005-11-15 | Networks Associates Technology, Inc. | System and method for remote maintenance of handheld computers |
| US7080000B1 (en) * | 2001-03-30 | 2006-07-18 | Mcafee, Inc. | Method and system for bi-directional updating of antivirus database |
| US7499948B2 (en) | 2001-04-16 | 2009-03-03 | Bea Systems, Inc. | System and method for web-based personalization and ecommerce management |
| US20020156877A1 (en) * | 2001-04-23 | 2002-10-24 | Lu James C. | System and method for the duplication of a software system onto an appropriate target computer |
| US6912591B2 (en) | 2001-05-02 | 2005-06-28 | Science Application International Corporation | System and method for patch enabled data transmissions |
| US7392546B2 (en) | 2001-06-11 | 2008-06-24 | Bea Systems, Inc. | System and method for server security and entitlement processing |
| WO2003036609A1 (en) * | 2001-10-24 | 2003-05-01 | Bea Systems, Inc. | Portal administration tool |
| US7350226B2 (en) | 2001-12-13 | 2008-03-25 | Bea Systems, Inc. | System and method for analyzing security policies in a distributed computer network |
| US7028338B1 (en) * | 2001-12-18 | 2006-04-11 | Sprint Spectrum L.P. | System, computer program, and method of cooperative response to threat to domain security |
| US9392002B2 (en) * | 2002-01-31 | 2016-07-12 | Nokia Technologies Oy | System and method of providing virus protection at a gateway |
| US6785820B1 (en) * | 2002-04-02 | 2004-08-31 | Networks Associates Technology, Inc. | System, method and computer program product for conditionally updating a security program |
| US7099899B2 (en) * | 2002-04-23 | 2006-08-29 | International Business Machines Corporation | System and method for item versioning in a content mangement system |
| US7496687B2 (en) * | 2002-05-01 | 2009-02-24 | Bea Systems, Inc. | Enterprise application platform |
| US7725560B2 (en) | 2002-05-01 | 2010-05-25 | Bea Systems Inc. | Web service-enabled portlet wizard |
| US6999976B2 (en) * | 2002-05-29 | 2006-02-14 | International Business Machines Corporation | Method, apparatus, and program for using a Java archive to encode a file system delta |
| CN1331045C (en) * | 2002-08-19 | 2007-08-08 | 万达信息股份有限公司 | Software automatic upgrading and updating method under Client/Server frame |
| US7577948B2 (en) * | 2003-07-02 | 2009-08-18 | Upgradedetect, Inc. | System and method for providing computer upgrade information |
| US6711676B1 (en) * | 2002-10-15 | 2004-03-23 | Zomaya Group, Inc. | System and method for providing computer upgrade information |
| CN100428753C (en) * | 2002-11-29 | 2008-10-22 | 英华达(上海)电子有限公司 | Method and system for implementing program updating by use of hypertext transmission protocol service |
| US8831966B2 (en) | 2003-02-14 | 2014-09-09 | Oracle International Corporation | Method for delegated administration |
| US7653930B2 (en) | 2003-02-14 | 2010-01-26 | Bea Systems, Inc. | Method for role and resource policy management optimization |
| US7591000B2 (en) | 2003-02-14 | 2009-09-15 | Oracle International Corporation | System and method for hierarchical role-based entitlements |
| US7415478B2 (en) | 2003-02-20 | 2008-08-19 | Bea Systems, Inc. | Virtual repository complex content model |
| US7840614B2 (en) | 2003-02-20 | 2010-11-23 | Bea Systems, Inc. | Virtual content repository application program interface |
| US7562298B2 (en) * | 2003-02-20 | 2009-07-14 | Bea Systems, Inc. | Virtual content repository browser |
| US7293286B2 (en) | 2003-02-20 | 2007-11-06 | Bea Systems, Inc. | Federated management of content repositories |
| US7483904B2 (en) * | 2003-02-20 | 2009-01-27 | Bea Systems, Inc. | Virtual repository content model |
| US20040167880A1 (en) * | 2003-02-20 | 2004-08-26 | Bea Systems, Inc. | System and method for searching a virtual repository content |
| US20040167871A1 (en) * | 2003-02-20 | 2004-08-26 | Bea Systems, Inc. | Content mining for virtual content repositories |
| US7810036B2 (en) | 2003-02-28 | 2010-10-05 | Bea Systems, Inc. | Systems and methods for personalizing a portal |
| US7644432B2 (en) | 2003-10-10 | 2010-01-05 | Bea Systems, Inc. | Policy inheritance through nested groups |
| US7594224B2 (en) | 2003-10-10 | 2009-09-22 | Bea Systems, Inc. | Distributed enterprise security system |
| US7774601B2 (en) * | 2004-04-06 | 2010-08-10 | Bea Systems, Inc. | Method for delegated administration |
| US7475091B2 (en) * | 2004-04-13 | 2009-01-06 | Bea Systems, Inc. | System and method for viewing a virtual content repository |
| US7236990B2 (en) * | 2004-04-13 | 2007-06-26 | Bea Systems, Inc. | System and method for information lifecycle workflow integration |
| US7246138B2 (en) * | 2004-04-13 | 2007-07-17 | Bea Systems, Inc. | System and method for content lifecycles in a virtual content repository that integrates a plurality of content repositories |
| US20050228816A1 (en) * | 2004-04-13 | 2005-10-13 | Bea Systems, Inc. | System and method for content type versions |
| US20050251503A1 (en) * | 2004-04-13 | 2005-11-10 | Bea Systems, Inc. | System and method for content and schema versioning |
| US20050251512A1 (en) * | 2004-04-13 | 2005-11-10 | Bea Systems, Inc. | System and method for searching a virtual content repository |
| US7236989B2 (en) * | 2004-04-13 | 2007-06-26 | Bea Systems, Inc. | System and method for providing lifecycles for custom content in a virtual content repository |
| US20050240714A1 (en) * | 2004-04-13 | 2005-10-27 | Bea Systems, Inc. | System and method for virtual content repository deployment |
| US20060028252A1 (en) * | 2004-04-13 | 2006-02-09 | Bea Systems, Inc. | System and method for content type management |
| US7240076B2 (en) * | 2004-04-13 | 2007-07-03 | Bea Systems, Inc. | System and method for providing a lifecycle for information in a virtual content repository |
| US7580953B2 (en) * | 2004-04-13 | 2009-08-25 | Bea Systems, Inc. | System and method for schema lifecycles in a virtual content repository that integrates a plurality of content repositories |
| US20060041558A1 (en) * | 2004-04-13 | 2006-02-23 | Mccauley Rodney | System and method for content versioning |
| WO2006110979A1 (en) | 2005-04-18 | 2006-10-26 | Research In Motion Limited | Implementing data-compatibility-based version scheme |
| US7953734B2 (en) * | 2005-09-26 | 2011-05-31 | Oracle International Corporation | System and method for providing SPI extensions for content management system |
| US7483893B2 (en) | 2005-09-26 | 2009-01-27 | Bae Systems, Inc. | System and method for lightweight loading for managing content |
| US7818344B2 (en) | 2005-09-26 | 2010-10-19 | Bea Systems, Inc. | System and method for providing nested types for content management |
| US7917537B2 (en) | 2005-09-26 | 2011-03-29 | Oracle International Corporation | System and method for providing link property types for content management |
| US7752205B2 (en) | 2005-09-26 | 2010-07-06 | Bea Systems, Inc. | Method and system for interacting with a virtual content repository |
| US7665081B1 (en) | 2006-05-06 | 2010-02-16 | Kaspersky Lab, Zao | System and method for difference-based software updating |
| US8055096B2 (en) * | 2006-05-10 | 2011-11-08 | Research In Motion Limited | Method and system for incremental patching of binary files |
| DE602006016096D1 (en) * | 2006-06-26 | 2010-09-23 | Research In Motion Ltd | Method and system for generating a reverse binary correction |
| US7779401B2 (en) | 2006-06-26 | 2010-08-17 | Research In Motion Limited | Method and system for generating a reverse binary patch for undoing a software update |
| US8463852B2 (en) | 2006-10-06 | 2013-06-11 | Oracle International Corporation | Groupware portlets for integrating a portal with groupware systems |
| US8572738B2 (en) * | 2006-12-07 | 2013-10-29 | International Business Machines Corporation | On demand virus scan |
| US8438558B1 (en) | 2009-03-27 | 2013-05-07 | Google Inc. | System and method of updating programs and data |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB9224176D0 (en) * | 1992-11-18 | 1993-01-06 | Calluna Tech Ltd | Miniature hard disk drive system |
| TW313643B (en) * | 1994-12-14 | 1997-08-21 | At & T Corp | |
| US6009480A (en) * | 1997-09-12 | 1999-12-28 | Telxon Corporation | Integrated device driver wherein the peripheral downloads the device driver via an I/O device after it is determined that the I/O device has the resources to support the peripheral device |
| US5924096A (en) * | 1997-10-15 | 1999-07-13 | Novell, Inc. | Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand |
| US5999179A (en) * | 1997-11-17 | 1999-12-07 | Fujitsu Limited | Platform independent computer network management client |
-
1998
- 1998-06-03 US US09/089,930 patent/US6167407A/en not_active Expired - Lifetime
-
1999
- 1999-06-02 EP EP99927158A patent/EP1082651B1/en not_active Expired - Lifetime
- 1999-06-02 CA CA002334004A patent/CA2334004C/en not_active Expired - Fee Related
- 1999-06-02 WO PCT/US1999/012228 patent/WO1999063432A2/en active IP Right Grant
- 1999-06-02 DE DE69905158T patent/DE69905158T2/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| CA2334004A1 (en) | 1999-12-09 |
| DE69905158D1 (en) | 2003-03-06 |
| EP1082651B1 (en) | 2003-01-29 |
| WO1999063432A2 (en) | 1999-12-09 |
| DE69905158T2 (en) | 2003-07-17 |
| WO1999063432A3 (en) | 2000-02-24 |
| US6167407A (en) | 2000-12-26 |
| EP1082651A2 (en) | 2001-03-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2334004C (en) | Backtracked incremental updating | |
| US6349311B1 (en) | Storage of reverse delta updates | |
| US7103794B2 (en) | Network object cache engine | |
| US7716342B2 (en) | Method and system for file-system based caching | |
| US7343412B1 (en) | Method for maintaining and managing dynamic web pages stored in a system cache and referenced objects cached in other data stores | |
| US5752042A (en) | Server computer for selecting program updates for a client computer based on results of recognizer program(s) furnished to the client computer | |
| US8417686B2 (en) | Web crawler scheduler that utilizes sitemaps from websites | |
| US6564218B1 (en) | Method of checking the validity of a set of digital information, and a method and an apparatus for retrieving digital information from an information source | |
| US6212557B1 (en) | Method and apparatus for synchronizing upgrades in distributed network data processing systems | |
| US8190577B2 (en) | Central database server apparatus and method for maintaining databases on application servers | |
| US6405219B2 (en) | Method and system for automatically updating the version of a set of files stored on content servers | |
| US6074434A (en) | Selection of code updates, data updates or new data for client | |
| US6061686A (en) | Updating a copy of a remote document stored in a local computer system | |
| US6457046B1 (en) | Information providing apparatus for server and computer-readable recording medium storing information providing program for server | |
| CN104820602A (en) | Method, device and system for publishing software package | |
| US20030187957A1 (en) | Automatic data download system and method | |
| US6986134B1 (en) | Lightweight global distribution mechanism | |
| US6883020B1 (en) | Apparatus and method for filtering downloaded network sites | |
| US6941430B2 (en) | Mirrored disk partition with disk partition modification contemporaneous with client application access | |
| WO1998057265A1 (en) | Network object cache engine | |
| US20060136501A1 (en) | Method and apparatus for saving and restoring parameter values set with user commands | |
| WO1998020426A1 (en) | External cache for on-line resources | |
| WO1998020426A9 (en) | External cache for on-line resources | |
| US9639547B2 (en) | Method and system for file-system based caching | |
| GB2347528A (en) | Object database with caching support |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20190603 |