Method for managing file replication in applications

RELATED APPLICATIONS

P-0001[0001] This patent application relates to commonly assigned copending U.S. patent application Ser. No. AA/BBB,CCC, filed Feb. 27, 2003 under attorney docket number MSFT-1586 and entitled “Method and System for Managing Multiple File States.”

FIELD OF THE INVENTION

[0002] The present invention is directed to methods for managing multiple versions of an electronic file. More particularly, the present invention relates to methods for using relevant application functionality to reconcile versions of a file during a synchronization event.

BACKGROUND OF THE INVENTION

[0003] It is common practice in a networked computer environment for a computer user to collaborate on an electronic document with another user on the network. Such a network may be a Local Area Network (LAN), Wide Area Network (WAN), the Internet or the like. In such a collaboration, each user may create and edit an electronic file by using a software application such as general application software, or software designed specifically for the type of file that is the object of the collaboration, or the like.

[0004] The collaboration may be made possible by maintaining a master version of the electronic file in a location that is accessible to all users who will be collaborating on the file. In a conventional networked computer environment, there may exist a server computer and one or more user computers. The server maintains communications links between, and is accessible to, each user computer and therefore may store and control the master version of the file being collaborated on by the users. When collaborating on an electronic file, a user may first access the master version of the file on the server, and then copy the file to the user's computer. The user may then work on the file by altering the file in any way made available to the user by the application. For example, if the application is a word processor, spreadsheet, database, and/or the like, the application may provide means for performing tasks such as editing, copying, deleting and/or the like. At the completion of any alterations, the user may save changes to the version of the file stored on the user's computer if the user wishes to retain such alterations to the file. In other systems, such as a system where no server computer exists, the master version may be stored on a user computer.

[0005] In order to collaborate with other users via the server, a user with a changed version stored on the user's computer must synchronize the version of the file on the computer with the master version of the file on the server. Synchronizing a plurality of versions of an electronic file, in its simplest form, ensures that all versions, once synchronized, are identical. In this way, the user performing the synchronization will enable other users who are participating in the collaboration to access the newly-altered file. Conventionally, a synchronization is performed by a synchronization utility. A synchronization utility is typically separate from the application, and in many cases is part of the operating system of the user computer. The conventional synchronization utility performs synchronizations at predetermined times, or as requested by the operating system.

[0006] In a conventional synchronization, a synchronization utility will compare the user version of the file to the master version of the file using whatever information about the copies the utility is able to comprehend. Typically, such information is limited to the date and/or time of the last update of each version. If the date and/or time is identical, the synchronization utility determines that both versions are identical, and therefore synchronized, and that no further action is required. If a discrepancy exists between the date and/or time, however, the synchronization utility provides the user associated with the computer that is driving the synchronization event with a user interface. The user interface conventionally provides a user with a brief notification that there is a discrepancy, the date and/or time of such last update for each version of the file, and a request for an instruction from the user as to which copy of the file the user wishes to keep. If the user elects to keep the user version, the synchronization utility overwrites the master version with the user version, thereby making the user version the new master version on the server. If the user desires to keep the master version, no further action is taken, or the user version is overwritten with the master version. In some user interfaces, a user is presented with an option to abort the synchronization, rather than choosing which version will be the master version.

[0007] The conventional synchronization as discussed above has significant disadvantages. Because a conventional synchronization utility has limited functionality with respect to an electronic file, a user interface generated by the conventional utility presents only a limited amount of information to a user when prompting a user to select a course of action. Such a limited amount of information may therefore cause such user to make an uninformed and possibly incorrect decision about which course of action to take. For example, a first user may alter a previously-synchronized user version of the file and then at some point the conventional synchronization utility initiates a synchronization event. When notified by the conventional user interface, the user may see that the user version was updated later than the master version and therefore decide to overwrite the master version. However, the information presented by the conventional user interface does not inform the user whether the master version has remained unchanged since the user began altering the user version. This leads to a problematic situation, where a second user may have made alterations to another user version, and then synchronized that user version with the master version before the first user's synchronization. The first user's version is more recent—having been updated later—but the master version has undergone alterations by the second user that were not present when the first user originally copied the file from the server. As a result, the second user's alterations to the master version are lost once the first user completes the synchronization.

[0008] The above situation is caused by a conventional synchronization utility's lack of the full range of functionality inherent in the application relevant to the file, so the utility is unable to use that functionality during a synchronization event. Therefore, the utility can only provide to a user a very limited amount of information regarding the different versions of the electronic file, such as, for example, the date and/or time of the last update to each version of the file as discussed above.

[0009] Another disadvantage caused by the limited functionality of conventional synchronization utilities is the lack of multiple courses of action available to a user during a synchronization. For example, in the example discussed above, the user interface only presents three options: update the master copy with the user copy, update the user copy with the master copy, or abort.

[0010] A further disadvantage of a conventional synchronization utility stems from a lack of integration of such utility with such application. For example, and as discussed above, a conventional synchronization utility is part of an operating system of a user or server computer. Therefore, the synchronization process, and any applicable user interface, is conventionally conducted outside of the application user experience. This may lead to confusion among users who—while such users may be proficient with the application—are not proficient with an operating system utility. Additionally, and as a result of the lack of integration, a synchronization may be initiated by the synchronization utility at a time that is not optimal for such event to take place. An additional disadvantage of conventional synchronization utilities is the inability of such a utility to be used as a component of a software application. For example, using conventional methods, a computer programmer is unable to create a first software application that uses a synchronization utility that as the ability to use a second application appropriate to the electronic file to reconcile multiple versions of the electronic file. Therefore, what is needed is an efficient means of using relevant software application functionality to resolve conflicts between copies of a file during a synchronization.

SUMMARY OF THE INVENTION

[0011] In view of the foregoing, the present invention provides methods of integrating an application program interface with a software application that allows the application to request and control a file synchronization process while remaining in the application user experience. The invention provides for a method for managing a first and second version of an electronic file. In the method, first and second versions of an electronic file are recognized and a synchronization event is initiated using a first software application operating on a first computer. An application program interface accesses the first and second versions, compares information associated with each, generates a result and reports the result to the first software application. A second software application generates a user interface in accordance with a feature of the second software application, where the electronic file is associated with the second software application, and the user interface is displayed on a display device.

[0012] The invention also provides for the second software application to generate a synchronization option and to present the option with the user interface and to display the user interface the display device. The second software application may also receive an option selection and synchronizes the first and second versions of the electronic file accordingly. The invention further provides that the first software application and the second software application may be the same software application. The application may provide any amount of information to the user regarding the first and second versions, and the user may input any number or type of synchronization selections. In one embodiment, the user may create a third version comprising any portion, or none, of either first or second version, or both. The application may initiate the synchronization at any time, such as at the user's request. Additional features and advantages of the invention are set forth in the description below.

BRIEF DESCRIPTION OF THE DRAWINGS

P-0013[0013] The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary embodiments of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:

P-0014[0014]FIG. 1 is a block diagram showing an exemplary computing environment in which aspects of the invention may be implemented;

P-0015[0015]FIG. 2 is a functional diagram illustrating an example of a relationship between a first computer, a network and a second computer;

P-0016[0016]FIG. 3 is a flowchart showing a synchronization process in accordance with one embodiment of the present invention; and

P-0017[0017]FIG. 4 is a flowchart illustrating a method of initiating a synchronization process in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

P-0018[0018] Overview

P-0019[0019] The present invention provides methods of integrating an application program interface with a software application that allows the application to request and control a file synchronization process while remaining in the application user experience. The invention provides for a method for managing a first and second version of an electronic file. In the method, first and second versions of an electronic file are recognized and a synchronization event to synchronize the first version on the first computer with the second version is initiated using a first software application operating on a first computer. An application program interface accesses the first and second versions, information associated with each of the first and second versions is compared and a result is generated. The result of the comparison is reported to the first software application. A second software application is caused to generate a user interface in accordance with a feature of the second software application, wherein the electronic file is associated with the second software application, and the user interface is displayed on a display device.

P-0020[0020] The invention also provides for the second software application to generate a synchronization option and to cause the synchronization option to be presented by the user interface and displayed on the display device. The second software application also receives an option selection and synchronizes the first and second versions of the electronic file according to the option selection. The invention further provides that the first software application and the second software application may be the same software application, and therefore all steps may be performed by a single application.

P-0021[0021] The application may provide any amount of information to the user regarding the first and second versions, and the user may input any number or type of synchronization selections. In one embodiment, the user may create a third version comprising any portion, or none, of either first or second version, or both. The application may initiate the synchronization at any time, such as at the user's request.

P-0022[0022] Exemplary Computing Environment

P-0023[0023]FIG. 1 illustrates an example of a suitable computing system environment <b>100</b> in which the invention may be implemented. The computing system environment <b>100</b> is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment <b>100</b> be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment <b>100</b>.

P-0024[0024] The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

P-0025[0025] The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network or other data transmission medium. In a distributed computing environment, program modules and other data may be located in both local and remote computer storage media including memory storage devices.

P-0026[0026] With reference to FIG. 1, an exemplary system for implementing the invention includes a general purpose computing device in the form of a computer <b>110</b>. Components of computer <b>110</b> may include, but are not limited to, a processing unit <b>120</b>, a system memory <b>130</b>, and a system bus <b>121</b> that couples various system components including the system memory to the processing unit <b>120</b>. The system bus <b>121</b> may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus (also known as Mezzanine bus).

P-0027[0027] Computer <b>110</b> typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer <b>110</b> and includes both volatile and non-volatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer <b>110</b>. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.

P-0028[0028] The system memory <b>130</b> includes computer storage media in the form of volatile and/or non-volatile memory such as ROM <b>131</b> and RAM <b>132</b>. A basic input/output system <b>133</b> (BIOS), containing the basic routines that help to transfer information between elements within computer <b>110</b>, such as during start-up, is typically stored in ROM <b>131</b>. RAM <b>132</b> typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit <b>120</b>. By way of example, and not limitation, FIG. 1 illustrates operating system <b>134</b>, application programs <b>135</b>, other program modules <b>136</b>, and program data <b>137</b>.

P-0029[0029] The computer <b>110</b> may also include other removable/non-removable, volatile/non-volatile computer storage media. By way of example only, FIG. 1 illustrates a hard disk drive <b>140</b> that reads from or writes to non-removable, non-volatile magnetic media, a magnetic disk drive <b>151</b> that reads from or writes to a removable, non-volatile magnetic disk <b>152</b>, and an optical disk drive <b>155</b> that reads from or writes to a removable, non-volatile optical disk <b>156</b>, such as a CD-ROM or other optical media. Other removable/non-removable, volatile/non-volatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive <b>141</b> is typically connected to the system bus <b>121</b> through a non-removable memory interface such as interface <b>140</b>, and magnetic disk drive <b>151</b> and optical disk drive <b>155</b> are typically connected to the system bus <b>121</b> by a removable memory interface, such as interface <b>150</b>.

P-0030[0030] The drives and their associated computer storage media, discussed above and illustrated in FIG. 1, provide storage of computer readable instructions, data structures, program modules and other data for the computer <b>110</b>. In FIG. 1, for example, hard disk drive <b>141</b> is illustrated as storing operating system <b>144</b>, application programs <b>145</b>, other program modules <b>146</b>, and program data <b>147</b>. Note that these components can either be the same as or different from operating system <b>134</b>, application programs <b>135</b>, other program modules <b>136</b>, and program data <b>137</b>. Operating system <b>144</b>, application programs <b>145</b>, other program modules <b>146</b>, and program data <b>147</b> are given different numbers here to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer <b>110</b> through input devices such as a keyboard <b>162</b> and pointing device <b>161</b>, commonly referred to as a mouse, trackball or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit <b>120</b> through a user input interface <b>160</b> that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor <b>191</b> or other type of display device is also connected to the system bus <b>121</b> via an interface, such as a video interface <b>190</b>. In addition to the monitor, computers may also include other peripheral output devices such as speakers <b>197</b> and printer <b>196</b>, which may be connected through an output peripheral interface <b>190</b>.

P-0031[0031] The computer <b>110</b> may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer <b>180</b>. The remote computer <b>180</b> may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer <b>110</b>, although only a memory storage device <b>181</b> has been illustrated in FIG. 1. The logical connections depicted include a local area network (LAN) <b>171</b> and a wide area network (WAN) <b>173</b>, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

P-0032[0032] When used in a LAN networking environment, the computer <b>110</b> is connected to the LAN <b>171</b> through a network interface or adapter <b>170</b>. When used in a WAN networking environment, the computer <b>110</b> typically includes a modem <b>172</b> or other means for establishing communications over the WAN <b>173</b>, such as the Internet. The modem <b>172</b>, which may be internal or external, may be connected to the system bus <b>121</b> via the user input interface <b>160</b>, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer <b>110</b>, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG. 1 illustrates remote application programs <b>185</b> as residing on memory device <b>181</b>. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

P-0033[0033] Exemplary Distributed Computing Frameworks Or Architectures Various distributed computing frameworks have been and are being developed in light of the convergence of personal computing and the Internet. Individuals and business users alike are provided with a seamlessly interoperable and web-enabled interface for applications and computing devices, making computing activities increasingly web browser or network-oriented.

P-0034[0034] For example, MICROSOFT®'s NET platform includes servers, building-block services, such as web-based data storage, and downloadable device software. Generally speaking, the .NET platform provides (1) the ability to make the entire range of computing devices work together and to have user information automatically updated and synchronized on all of them, (2) increased interactive capability for web sites, enabled by greater use of XML rather than HTML, (3) online services that feature customized access and delivery of products and services to the user from a central starting point for the management of various applications, such as e-mail, for example, or software, such as Office .NET, (4) centralized data storage, which will increase efficiency and ease of access to information, as well as synchronization of information among users and devices, (5) the ability to integrate various communications media, such as e-mail, faxes, and telephones, (6) for developers, the ability to create reusable modules, thereby increasing productivity and reducing the number of programming errors, and (7) many other cross-platform integration features as well.

P-0035[0035] While exemplary embodiments herein are described in connection with software residing on a computing device, one or more portions of the invention may also be implemented via an operating system, API, or a “middle man” object between a coprocessor and requesting object, such that services may be performed by, supported in, or accessed via all of NET's languages and services, and in other distributed computing frameworks as well.

P-0036[0036] Exemplary Embodiments

P-0037[0037] When an electronic file has been formed into more than one version, according to the invention, an application program interface may be configured to allow a software application associated with the file to control a process of synchronizing the plurality of versions. In one embodiment, the application may initiate the synchronization automatically, while in another embodiment, the application may initiate the synchronization based on user input. In another embodiment, the application presents synchronization options provided by application functionality to the user, and permits the user to select options and perform tasks using the application functionality. In yet another embodiment, a first application initiates the synchronization, while a second application presents synchronization options to a user.

P-0038[0038] Referring now to FIG. 2, a first computer <b>210</b> comprises a first processor <b>220</b> in operative communication with a storage device <b>218</b>. First computer <b>210</b> may be a general purpose desktop or portable computer, a workstation, a specialized computing device and/or the like. Likewise, first processor <b>220</b> may be a general purpose computer processor, a specialized processor, a network of processors or the like. Operatively associated with first computer <b>210</b> is display device <b>230</b>. Display device <b>230</b> may be any means of presenting options and the like to a user, such as for example a monitor, speakers or the like. Such operative association of display device <b>230</b> to first computer <b>210</b> may be made by any wired or wireless connective means. While display device <b>230</b> is shown to be within first computer <b>210</b> in FIG. 2, display device <b>230</b> may be located anywhere that is in operative communications with first processor <b>220</b>, to include a remote location or the like.

P-0039[0039] Storage device <b>218</b> may be a hard drive, CD-ROM, magnetic disk, DVD, RAM and/or the like. Like display device <b>230</b>, storage device <b>218</b> may be located anywhere that is in operative communications with first processor <b>220</b>. Operative communications in such a situation may be wired, wireless or any combination thereof. Contained within storage device <b>218</b> is a first version <b>212</b> of an electronic file. Such first version <b>212</b> may be any type of electronic file, such as for example a word processing document, spreadsheet, database and/or the like.

P-0040[0040] First application <b>208</b> and second application <b>214</b> may be stored in storage device <b>218</b>. First application <b>208</b> and second application <b>214</b> may be any type of computer-executable instructions, such as for example a word processor, spreadsheet, database, programmed script, specialized software or the like. In embodiments where both first application <b>208</b> and second application <b>214</b> are present, as discussed below, only second application <b>214</b> need be compatible with the electronic file. Alternatively, and as will also be discussed below, first application <b>208</b> and second application <b>214</b> may be the same application. One or both of first application <b>208</b> and second application <b>214</b> may also be located outside of storage device <b>218</b>, as either application need only be in operative communications with first computer <b>210</b>.

P-0041[0041] Application program interface <b>216</b> is any type of computer-executable instructions adapted to check and compare two or more copies of an electronic file for synchronization purposes, and may be stand alone software that is specifically designed for synchronizing two or more copies of an electronic document, a software utility that operates as a component of another application, an integrated component of first or second application <b>208</b>, <b>214</b> and/or the like. Application program interface <b>216</b> may also perform additional tasks that may or may not be related to synchronization. First version <b>212</b>, first application <b>208</b>, second application <b>214</b> and application program interface <b>216</b> may reside in the same storage device <b>218</b>, or within or across any number different storage devices <b>218</b>.

P-0042[0042] Second computer <b>222</b> comprises a second processor <b>224</b> and storage device <b>228</b> which contains a second version <b>226</b> of the electronic file discussed above in connection with first version <b>212</b>. As discussed above, storage device <b>228</b> may be located anywhere that is in operative communications with second computer <b>222</b>, to include a remote location or the like. Also, storage device <b>228</b> and storage device <b>218</b> may, in an embodiment, be the same storage device. Operatively connecting first and second computers <b>210</b>, <b>222</b> is network <b>218</b>. Network <b>218</b> may be any communications network adapted for such operative communications, such as for example a LAN, WAN, wireless network or the like. As may be appreciated, any number of first computers <b>210</b> and second computers <b>222</b> may be operatively connected to network <b>218</b>.

P-0043[0043] Turning now to FIG. 3, at step <b>311</b> a synchronization process begins. In one embodiment, first application <b>208</b> initiates the synchronization process, and second application <b>214</b> carries out the synchronization process. In another embodiment, first application <b>208</b> and second application <b>214</b> are a single application, in which case the single application both initiates and carries out the synchronization. While the discussion of FIG. 3 that follows describes a process involving both first application <b>208</b> and second application <b>214</b>, it may be appreciated that a single application may alone perform all of the steps performed by first application <b>208</b> and second application <b>214</b>.

P-0044[0044] Any number of situations may cause first application <b>208</b> to initiate a synchronization process, such as for example: opening, closing, saving or the like of first version <b>212</b>; upon recognizing a first and second version of the electronic file; manually initiating upon a user request; initiating at timed intervals; upon a user logging into a system and/or the like. In addition, first application <b>208</b> may impose any additional conditions or may use substitute conditions such as, for example, only initiating a synchronization when a certain number of versions are present. More details with respect to initiating a synchronization event in one embodiment follows below in connection with FIG. 4. To initiate the process, first application <b>208</b> causes application program interface <b>216</b> to access first version <b>212</b> and second version <b>226</b>. Accessing first version <b>212</b> and second version <b>226</b> may be performed by any computing means, such as by viewing information associated with each version, finding each version by using searching functionality, locating each version by using identifying information provided by first application <b>208</b> or the like.

P-0045[0045] First application <b>208</b> may provide interface <b>216</b> with any amount of identifying information about second version <b>226</b>, such as for example a file name, location, address and/or the like. Interface <b>216</b> may be adapted to actively locate second version <b>226</b>, or may have limited functionality that permits only looking at a location specified by first application <b>208</b>, first version <b>212</b> or the like. Also, interface <b>216</b> may be configured to perform any number of additional tasks that may even be unrelated to the synchronization process. At step <b>313</b>, application program interface <b>216</b> locates second version <b>226</b> and checks for a synchronization status. The application program interface <b>216</b> determines the status by comparing information, such as for example time and/or date of a last update or the like, for first version <b>212</b> against second version <b>226</b>. Synchronization status may also be determined by any criteria additional to or substituted for the information mentioned above. If the information matches information and/or criteria specified by first application <b>208</b>, first and second versions <b>212</b>, <b>226</b> have a synchronized status. If the information is inconsistent, first and second versions <b>212</b>, <b>226</b> do not have a synchronized status, as such an inconsistency indicates the possibility that changes may have been made to one of such versions <b>212</b>, <b>226</b>. Alternatively, if application program interface <b>216</b> detects an error, a condition not provided for, a condition that first application <b>208</b> has specified as cause for terminating the synchronization, or the like, then interface <b>216</b> proceeds to step <b>330</b>. At step <b>330</b>, interface <b>216</b> informs first application <b>208</b> of the condition and first application <b>208</b> proceeds accordingly, which may include any type of action or inaction.

P-0046[0046] At step <b>315</b>, application program interface <b>216</b> may take one of two courses of action depending on the outcome of the synchronization determination of step <b>313</b>. If application program interface <b>216</b> has determined that first version <b>212</b> and second version <b>226</b> are synchronized, interface <b>216</b> proceeds to step <b>325</b>. At step <b>325</b>, application program interface reports to first application <b>208</b> that first version <b>212</b> and second version <b>226</b> are synchronized. Such a report indicates to first application <b>208</b> that no further synchronization activities are presently necessary, as first version <b>212</b> comprises the most recent version of the electronic file. The report may also indicate that a user may use first application <b>208</b> or second application <b>214</b> to alter first version <b>212</b>.

P-0047[0047] At step <b>323</b>, the synchronization process ends. At this step, first application <b>208</b> may cease functioning, such as for example if such synchronization process took place when first application <b>208</b> was closing first version <b>212</b> of the electronic document. In such a situation, once synchronization has occurred, therefore, first application <b>208</b> has no more functions to perform and may terminate manually by user or automatically. In another embodiment, first application <b>208</b> initiates the synchronization process when opening a first version <b>212</b>. In such a situation, application would not terminate at the completion of such synchronization event, and rather would permit user to begin altering first version <b>212</b> using first application <b>208</b> functionality, if available.

P-0048[0048] If, at step <b>315</b>, however, application program interface <b>216</b> has determined that first version <b>212</b> and second version <b>226</b> are not synchronized, interface <b>216</b> proceeds to step <b>317</b>. At step <b>317</b>, application program interface <b>216</b> reports to first application <b>208</b> and/or second application <b>214</b> that first version <b>212</b> and second version <b>226</b> are not synchronized. Such a report causes second application <b>214</b> to begin synchronizing first version <b>212</b> and second version <b>226</b> with user input as discussed below in connection with steps <b>319</b> and <b>321</b>.

P-0049[0049] At step <b>319</b>, second application <b>214</b> presents a user interface to a user by displaying the user interface on a display device <b>230</b>. Such user interface may be in the form of a text and/or graphics window, audio prompt and/or the like, and any such configuration of a user interface is equally consistent with an embodiment of the present invention. In presenting such user interface, second application <b>214</b> may present one or more options to a user using second application <b>214</b> functionality or the like. For example, if second application <b>214</b> is a word processor, second application <b>214</b> may present a synchronization option to a user within a word processing user environment of second application <b>214</b>, such as for example an editing window with a page view of such first version <b>212</b> and/or the like. Also, second application <b>214</b> may highlight differences between first version <b>212</b> and second version <b>226</b> using color, sounds, graphics and the like to better enable user to make synchronization decisions. Second application <b>214</b> may also provide additional information, such as for example the identity of each user who altered either version <b>212</b>, <b>226</b>, and may only permit a user to alter a version <b>212</b>, <b>226</b> if such user has permission, in the form of a security clearance or the like, to do so. Second application <b>214</b> may enable user to, for example, merge versions <b>212</b>, <b>226</b> into a third copy, so as to incorporate changes in both versions <b>212</b>, <b>226</b>. An additional option may also be in the form of guidance derived from second application <b>214</b> functionality such as for example a recommended course of action and/or the like. As may be appreciated, an option may be anything that may be generated by second application <b>214</b> using second application <b>214</b> functionality with respect to first version <b>212</b> and second version <b>226</b>.

P-0050[0050] At step <b>321</b>, second application <b>214</b> receives and processes user input. Such user input may comprise any amount of information regarding such synchronization. For example, user input may select a particular alteration of either first version <b>212</b> or second version <b>226</b> of the electronic file that the user wishes to retain. In another embodiment, user input may comprise a selection of either first version <b>212</b> or second version <b>226</b> that user wishes to retain in its entirety. In still another embodiment, user input may comprise edits of first and/or second version <b>212</b>, <b>226</b> using the functionality of second application <b>214</b> that, when completed, results in synchronizing first version <b>212</b> and second version <b>226</b>. As may be appreciated, user input may comprise any input made available by second application <b>214</b> for selection or use by a user, and any such input is consistent with an embodiment of the present invention.

P-0051[0051] As also may be appreciated, steps <b>319</b> and <b>321</b> may repeat, as such user interface may be redisplayed and/or refreshed depending on user input. For example, user interface may be reconfigured by second application <b>214</b> based on user input. Such a reconfiguration may occur if, for example, user selects one of a plurality of differences between first version <b>212</b> and second version <b>226</b> and second application <b>214</b> redisplays user interface to user to reflect such a selection. Steps <b>319</b> and <b>321</b> may repeat any number of times, or not at all, and either such situation is equally consistent with an embodiment of the present invention. Also, second application <b>214</b> may report any results of the synchronization to first application <b>208</b> or to interface <b>216</b>. The results reported by second application <b>214</b> may be any information associated with the synchronization, such as the option selection(s), synchronization result(s) or the like.

P-0052[0052] Second application <b>214</b> may proceed to step <b>323</b>, the end of the synchronization, when a triggering event occurs. Such triggering event may occur at any time, such as for example when user has completed reconciling all differences between first version <b>212</b> and second version <b>226</b>, when user directs second application <b>214</b> to abort or terminate the synchronization process without completing synchronization, at a predefined time, or the like. At step <b>323</b>, the synchronization ends. First application <b>208</b> or second application <b>214</b> may then, as mentioned above in connection with step <b>325</b>, take any action at step <b>323</b> that is consistent with the context in which the synchronization took place.

P-0053[0053] Turning now to FIG. 4, a detailed view of step <b>311</b> is shown in accordance with one embodiment of the present invention. As discussed above in connection with FIG. 3, in step <b>311</b> first application <b>208</b> initiates a synchronization process. FIG. 4 illustrates with greater particularity one embodiment of such an initiation step, where first application <b>208</b> initiates such synchronization process upon opening first version <b>212</b> of an electronic file. As discussed above, first application <b>208</b> may initiate such synchronization process at any time, such as for example when opening, saving or closing such first version <b>212</b>, at set or variable intervals, upon user inputs and/or the like.

P-0054[0054] At step <b>411</b>, first application <b>208</b> opens first version <b>212</b> of an electronic file. Such opening will most commonly occur upon user input to open such first version <b>212</b>, but any means for initiating such opening of first version <b>212</b> is consistent with an embodiment of the present invention. At step <b>413</b>, first application <b>208</b> determines whether first version <b>212</b> has an associated second version <b>226</b>. first application <b>208</b> may proceed to step <b>413</b> upon completely opening first version <b>212</b> in step <b>411</b>, or may proceed to step <b>413</b> at any point during such opening process including, for example, before opening first version <b>212</b> at step <b>411</b>. Also, any method may be employed to enable first application <b>208</b> to make such a determination. For example, information such as an electronic stamp or the like may be associated with such first version <b>212</b> thereby enabling first application <b>208</b> to make such determination. In contrast, first application <b>208</b> may search any or all computing devices operatively connected to network <b>218</b>, such as for example second computer <b>222</b>, for such determination. As may be appreciated, first application <b>208</b> may use any method of determining the existence of second version <b>226</b> while remaining consistent with an embodiment of the present invention.

P-0055[0055] If, at step <b>413</b>, first application <b>208</b> does not find second version <b>226</b> first application <b>208</b> determines that first version <b>212</b> is the only copy of such electronic file and proceeds to step <b>417</b>. At step <b>417</b> first application <b>208</b> processes first version <b>212</b> normally. Such normal processing may be any type of processing that first application <b>208</b> typically performs on electronic files of the same format as first version <b>212</b>, possibly in accordance with any user inputs. For example, in FIG. 4 first application <b>208</b> was in the process of opening first version <b>212</b> when first application <b>208</b> initiated such synchronization process according to step <b>311</b>. Upon finding no need for a synchronization—because of the absence of second version <b>226</b>—first application <b>208</b> completes opening of first version <b>212</b> and proceeds accordingly.

P-0056[0056] If, at step <b>413</b>, first application <b>208</b> finds second version <b>226</b> first application <b>208</b> proceeds to step <b>415</b>. At step <b>415</b>, first application <b>208</b> contacts application program interface <b>216</b> to commence synchronization of first version <b>212</b> and second version <b>226</b>. Upon contacting application program interface <b>216</b>, such synchronization process proceeds to step <b>313</b> as discussed above in connection with FIG. 3.

P-0057[0057] Thus, methods and apparatus for managing file replication in applications have been presented. While the present invention has been described in connection with the preferred embodiments of the various figures, it is to be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiment for performing the same function of the present invention without deviating therefrom. For example, one skilled in the art will recognize that the present invention as described in the present application may apply to any computing device or environment, whether wired or wireless, and may be applied to any number of such computing devices connected via a communications network, and interacting across the network. Furthermore, it should be emphasized that a variety of computer platforms, including handheld device operating systems and other application specific operating systems are contemplated, especially as the number of wireless networked devices continues to proliferate. Still further, the present invention may be implemented in or across a plurality of processing chips or devices, and storage may similarly be affected across a plurality of devices. Therefore, the present invention should not be limited to any single embodiment, but rather should be construed in breadth and scope in accordance with the appended claims.