Abstract: The present invention relates to new and improved embodiments of systems and methods for using a “pen” input as a temporary pointer to highlight a portion of a document and having the “ink” disappear. In embodiments, a method and system for temporarily marking a portion of a document comprises sending a marking directive that produces a visual indicia on a document being viewed on two or more display devices connected over a network, waiting a period of time, and automatically erasing the visual indicia on the document being viewed on the two or more display devices.

Abstract: Example systems, methods, and data structures are directed at synchronizing documents. One example data structure includes receiving a request from a first client to edit a document, and sending short-term check out metadata to the first client to begin an editing session. The data structure includes a plurality of cells and a plurality of data objects defining content of the document. Each data object is associated with one of the cells and has an object identifier that uniquely identifies the data object within the associated cell, and is configured to communicate with other cells and with objects within the associated cell. In addition, each of the cells is defined so that each other cell remains unaffected by changes to data objects of the cell.

Abstract: The present invention relates to new and improved embodiments of systems and methods for using a “pen” input as a temporary pointer to highlight a portion of a document and having the “ink” disappear. In embodiments, a method and system for temporarily marking a portion of a document comprises sending a marking directive that produces a visual indicia on a document being viewed on two or more display devices connected over a network, waiting a period of time, and automatically erasing the visual indicia on the document being viewed on the two or more display devices.

Abstract: Example systems, methods, and data structures are directed at synchronizing documents. One example data structure includes receiving a request from a first client to edit a document, and sending short-term check out metadata to the first client to begin an editing session. The data structure includes a plurality of cells and a plurality of data objects defining content of the document. Each data object is associated with one of the cells and has an object identifier that uniquely identifies the data object within the associated cell, and is configured to communicate with other cells and with objects within the associated cell. In addition, each of the cells is defined so that each other cell remains unaffected by changes to data objects of the cell.

Abstract: Contents of a copy of a server file may be saved to a down load file, a base file, and a working file. An indication may be received from an application that the application has edited the working file and a copy of the edited working file may be saved to an upload file. A server computer may be queried to determine if the server file on the server computer has been changed. If the server file on the server computer has not been changed, the server file on the server computer may be updated with contents of the upload file. If the server file on the server computer has been changed, a three-way merge of the upload file, the base file, and the changed server file on the server computer may be performed. Then the server file on the server computer may be updated with the three-way merge results.

Abstract: Many different users may access, revise and update the same shared object simultaneously through several different transports. Clients may communicate asynchronously by accessing the shared object through a physical server. Clients may also communicate synchronously by accessing the shared object through a peer-to-peer network. A manifest file associated with the shared object identifies the locations where other versions and instances of the shared object are stored. The shared object and the associated manifest file allow a client to transition seamlessly between local access, synchronous and asynchronous communication such that the user is not aware that the mode of communication has changed. A user may change location and any available data sharing transports are automatically identified. Thus, the user may access a shared object and collaborate with other authorized users through different mechanisms.

Abstract: Example systems, methods, and data structures are directed at synchronizing documents. One example data structure includes receiving a request from a first client to edit a document, and sending short-term check out metadata to the first client to begin an editing session. The data structure includes a plurality of cells and a plurality of data objects defining content of the document. Each data object is associated with one of the cells and has an object identifier that uniquely identifies the data object within the associated cell, and is configured to communicate with other cells and with objects within the associated cell. In addition, each of the cells is defined so that each other cell remains unaffected by changes to data objects of the cell.

Abstract: Many different users may access, revise and update the same shared object simultaneously through several different transports. Clients may communicate asynchronously by accessing the shared object through a physical server. Clients may also communicate synchronously by accessing the shared object through a peer-to-peer network. A manifest file associated with the shared object identifies the locations where other versions and instances of the shared object are stored. The shared object and the associated manifest file allow a client to transition seamlessly between local access, synchronous and asynchronous communication such that the user is not aware that the mode of communication has changed. A user may change location and any available data sharing transports are automatically identified. Thus, the user may access a shared object and collaborate with other authorized users through different mechanisms.

Abstract: Many different users may access, revise and update the same shared object simultaneously through several different transports. Clients may communicate asynchronously by accessing the shared object through a physical server. Clients may also communicate synchronously by accessing the shared object through a peer-to-peer network. A manifest file associated with the shared object identifies the locations where other versions and instances of the shared object are stored. The shared object and the associated manifest file allow a client to transition seamlessly between local access, synchronous and asynchronous communication such that the user is not aware that the mode of communication has changed. A user may change location and any available data sharing transports are automatically identified. Thus, the user may access a shared object and collaborate with other authorized users through different mechanisms.

Abstract: Tools and techniques are described for merging versions of documents using multiple masters. These tools may provide methods that include syncing a first peer system with at least a second peer system, with the first and second peer systems receiving respective instances of a document for collaborative editing. The first and second peer systems may maintain respective version histories associated with the document, with these version histories capturing and storing revisions occurring locally at the first and second peer systems. The first and second peer systems may exchange version histories, and merge these version histories.

Abstract: The present invention relates to new and improved embodiments of systems and methods for using a “pen” input as a temporary pointer to highlight a portion of a document and having the “ink” disappear. In embodiments, a method and system for temporarily marking a portion of a document comprises sending a marking directive that produces a visual indicia on a document being viewed on two or more display devices connected over a network, waiting a period of time, and automatically erasing the visual indicia on the document being viewed on the two or more display devices.

Abstract: The present invention relates to new and improved embodiments of systems and methods for using a “pen” input as a temporary pointer to highlight a portion of a document and having the “ink” disappear. In embodiments, a method and system for temporarily marking a portion of a document comprises sending a marking directive that produces a visual indicia on a document being viewed on two or more display devices connected over a network, waiting a period of time, and automatically erasing the visual indicia on the document being viewed on the two or more display devices.

Abstract: Tools and techniques are described for merging versions of documents using multiple masters. These tools may provide methods that include syncing a first peer system with at least a second peer system, with the first and second peer systems receiving respective instances of a document for collaborative editing. The first and second peer systems may maintain respective version histories associated with the document, with these version histories capturing and storing revisions occurring locally at the first and second peer systems. The first and second peer systems may exchange version histories, and merge these version histories.

Abstract: Example systems, methods, and data structures are directed at synchronizing documents. One example data structure includes receiving a request from a first client to edit a document, and sending short-term check out metadata to the first client to begin an editing session. The data structure includes a plurality of cells and a plurality of data objects defining content of the document. Each data object is associated with one of the cells and has an object identifier that uniquely identifies the data object within the associated cell, and is configured to communicate with other cells and with objects within the associated cell. In addition, each of the cells is defined so that each other cell remains unaffected by changes to data objects of the cell.

Abstract: Many different users may access, revise and update the same shared object simultaneously through several different transports. Revisions to the shared object are automatically synchronized such that all users can view the revisions to the shared object. Conflicting revisions are reconciled and merged into a current version of the shared object. A client may request the current version of the shared object from a store when the current version of the shared object is not available from the store. The current version of the shared object is synchronized with the client when the store receives the current version of the share object.

Abstract: Contents of a copy of a server file may be saved to a down load file, a base file, and a working file. An indication may be received from an application that the application has edited the working file and a copy of the edited working file may be saved to an upload file. A server computer may be queried to determine if the server file on the server computer has been changed. If the server file on the server computer has not been changed, the server file on the server computer may be updated with contents of the upload file. If the server file on the server computer has been changed, a three-way merge of the upload file, the base file, and the changed server file on the server computer may be performed. Then the server file on the server computer may be updated with the three-way merge results.

Abstract: Methods, systems, and computer program products disambiguate a globally universal identifier (GUID) within a file after the file is duplicated. The method involves generating a GUID for the file, generating a location identifier that defines a unique location of the file when the GUID was generated, and storing the location identifier in association with the GUID. The method also involves opening and examining the file, determining whether the location identifier matches a current location of the file, and in response to determining that the location identifier does not match the current location, generating a new GUID and replacing the GUID with the new GUID. Additionally, the method may also involve remapping references mapped to the GUID in the file to the new GUID and resetting the location identifier to match the current location.