WO1999063432A2 - Backtracked incremental updating - Google Patents
Backtracked incremental updating Download PDFInfo
- Publication number
- WO1999063432A2 WO1999063432A2 PCT/US1999/012228 US9912228W WO9963432A2 WO 1999063432 A2 WO1999063432 A2 WO 1999063432A2 US 9912228 W US9912228 W US 9912228W WO 9963432 A2 WO9963432 A2 WO 9963432A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- state
- hub
- final
- file
- sequence
- Prior art date
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
Definitions
- This invention pertains to the field of software updating. More specifically, this invention pertains to a system and method for using an archival version of a file to facilitate updating.
- 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 files begin to disappear, as the 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 grouping. This method of updating
- 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 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.
- 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.
- 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 ( 112) 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
- the second incremental update (112) is used (322) to produce the current version
- FIG 2 is an illustration of one embodiment of the present inv ention
- Fig 3 is a flowchart illustrating the operation of one embodiment of the present invention
- Fig 1 a sequence 100 of states 1.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 numencal designations Those versions with numencal designations ending in ".0" correspond to hub versions
- 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
- the computer readable file is a virus definition file used by a virus detection program
- the term 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 compnsmg files of different types, or any other type of computer readable file which can be accessed and updated by a computer
- two hub incremental updates 110 are each used to construct a hub version 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.0
- 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)
- 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
- archive file 206 is the latest hub version which is not later in sequence 100 than active file 208
- active file 208 is a hub version
- redundancy is avoided by stonng only one version of the file on computer 204, since both archive file 206 and active file 208 are the same file in that case.
- Archive 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 110 and 112, and updater 210, can be implemented using a conventional incremental update system, such as binary patching.
- archive file 206 is stored on computer 204 in a compressed form.
- This compressed form can be any conventional form of file compression.
- archive file 206 is stored on computer 204 in the form of a 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.
- Server 200 transmits an incremental update 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.
- server 200 can be a removable magnetic or optical storage medium, or any other type of storage device capable of supplying 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.
- active file 208 to be updated is selected 300 as the Original_State.
- the most recent 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.
- the most recent hub version available on server 200 is identified 306 by updater 210 as the Final_Hub. Ordinarily, the FinalJHub state will precede the Final_State in 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 FinalJHub 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.
- Final_Hub version is retained 324 on local computer 204 after FinaljState has been produced.
- the updating scheme used by updater 210 is one which replaces the file 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.
- the Final Hub version is archive file 206, and the FinaljState version is active file 208.
- each hub incremental update 110 is packaged with final incremental update 112 on server 200. This package is identified as corresponding to the OriginalJTub state to which the included hub incremental update 110 applies. Rather than determining what the FinalJHub and FinaljState are, updater 210 requests the package identified as being for Original_Hub state, extracts the included incremental updates, and applies them to OriginalJHub. If OriginalJHub is the same 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.
- updater 210 does not explicitly determine whether Original Hub is the same as Final_Hub, or whether FinalJHub is the same as FinaljState. For simplicity, only one file needs to be retrieved, and communication between updater 210 and server 200 is minimized. 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.
- JAR Java Archive
- the present invention permits updating from a small number of incremental updates retneved from a dumb server without requinng that a large number of incremental update files are stored on the server
- the incremental update files necessary for an update are stored on servers other than those controlled by the publisher
- 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
- 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
- the above descnption is included to illustrate the operation of
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE69905158T DE69905158T2 (en) | 1998-06-03 | 1999-06-02 | UPDATE INCREMENTAL |
EP99927158A EP1082651B1 (en) | 1998-06-03 | 1999-06-02 | Incremental updating |
CA002334004A CA2334004C (en) | 1998-06-03 | 1999-06-02 | Backtracked incremental updating |
Applications Claiming Priority (2)
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 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO1999063432A2 true WO1999063432A2 (en) | 1999-12-09 |
WO1999063432A3 WO1999063432A3 (en) | 2000-02-24 |
Family
ID=22220272
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1999/012228 WO1999063432A2 (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) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1168165A3 (en) * | 2000-06-30 | 2005-02-16 | International Business Machines Corporation | Device and method for updating code |
WO2006110979A1 (en) | 2005-04-18 | 2006-10-26 | Research In Motion Limited | Implementing data-compatibility-based version scheme |
US7412480B2 (en) | 2000-06-30 | 2008-08-12 | International Business Machines Corporation | Device and method for updating code |
Families Citing this family (67)
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 |
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 |
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 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0717353A2 (en) * | 1994-12-14 | 1996-06-19 | AT&T Corp. | Efficient and secure update of software and data |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB9224176D0 (en) * | 1992-11-18 | 1993-01-06 | Calluna Tech Ltd | Miniature hard disk drive system |
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
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0717353A2 (en) * | 1994-12-14 | 1996-06-19 | AT&T Corp. | Efficient and secure update of software and data |
Non-Patent Citations (1)
Title |
---|
"USER-FRIENDLY INTERFACE FOR APPLYING SPECIFIC LEVELS OF COORDINATED UPDATES TO SOFTWARE IN THE FIELD" IBM TECHNICAL DISCLOSURE BULLETIN,US,IBM CORP. NEW YORK, vol. 31, no. 10, page 258-259 XP000051138 ISSN: 0018-8689 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1168165A3 (en) * | 2000-06-30 | 2005-02-16 | International Business Machines Corporation | Device and method for updating code |
US7412480B2 (en) | 2000-06-30 | 2008-08-12 | International Business Machines Corporation | Device and method for updating code |
US7970821B2 (en) | 2000-06-30 | 2011-06-28 | International Business Machines Corporation | Device and method for updating code |
WO2006110979A1 (en) | 2005-04-18 | 2006-10-26 | Research In Motion Limited | Implementing data-compatibility-based version scheme |
EP1872215A1 (en) * | 2005-04-18 | 2008-01-02 | Research In Motion Limited | Implementing data-compatibility-based version scheme |
EP1872215A4 (en) * | 2005-04-18 | 2008-05-21 | Research In Motion Ltd | Implementing data-compatibility-based version scheme |
US7698702B2 (en) | 2005-04-18 | 2010-04-13 | Research In Motion Limited | System and method for implementing data-compatibility-based version scheme |
US8555272B2 (en) | 2005-04-18 | 2013-10-08 | Research In Motion Limited | System and method for implementing data-compatibility-based version scheme |
Also Published As
Publication number | Publication date |
---|---|
CA2334004A1 (en) | 1999-12-09 |
DE69905158D1 (en) | 2003-03-06 |
EP1082651B1 (en) | 2003-01-29 |
DE69905158T2 (en) | 2003-07-17 |
WO1999063432A3 (en) | 2000-02-24 |
US6167407A (en) | 2000-12-26 |
CA2334004C (en) | 2002-04-09 |
EP1082651A2 (en) | 2001-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6167407A (en) | Backtracked incremental updating | |
US6349311B1 (en) | Storage of reverse delta updates | |
US7103794B2 (en) | Network object cache engine | |
US6212557B1 (en) | Method and apparatus for synchronizing upgrades in distributed network data processing systems | |
US5752042A (en) | Server computer for selecting program updates for a client computer based on results of recognizer program(s) furnished to the client computer | |
US7185332B1 (en) | Multi-tiered incremental software updating | |
US6651249B2 (en) | Multi-tiered incremental software updating | |
US7539704B2 (en) | Method, apparatus, system, and program product for attaching files and other objects to a partially replicated database | |
US6405219B2 (en) | Method and system for automatically updating the version of a set of files stored on content servers | |
US7716342B2 (en) | Method and system for file-system based caching | |
EP0976065B1 (en) | Dynamic directory service | |
US6074434A (en) | Selection of code updates, data updates or new data for client | |
US6029166A (en) | System and method for generating an operating system-independent file map | |
US6408434B1 (en) | System and method for using a substitute directory to automatically install an update program | |
US20050273486A1 (en) | Virtual distributed file system | |
EP1351136A2 (en) | Delta replication of source files and packages across networked resources | |
US20040002982A1 (en) | Dynamic metabase store | |
US20110119236A1 (en) | Central database server apparatus and method for maintaining databases on application servers | |
JP2005539314A (en) | Apparatus and method for processing data in a network | |
US20030187957A1 (en) | Automatic data download system and method | |
US6941430B2 (en) | Mirrored disk partition with disk partition modification contemporaneous with client application access | |
EP1066571B1 (en) | Method, apparatus, system, and program product for attaching files and other objects to a partially replicated database | |
US20060136501A1 (en) | Method and apparatus for saving and restoring parameter values set with user commands | |
WO1998057265A1 (en) | Network object cache engine | |
WO1998020426A9 (en) | External cache for on-line resources |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): CA |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
AK | Designated states |
Kind code of ref document: A3 Designated state(s): CA |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
ENP | Entry into the national phase |
Ref document number: 2334004 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1999927158 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1999927158 Country of ref document: EP |
|
WWG | Wipo information: grant in national office |
Ref document number: 1999927158 Country of ref document: EP |