US20120254315A1 - Caching infrastructure - Google Patents
Caching infrastructure Download PDFInfo
- Publication number
- US20120254315A1 US20120254315A1 US13/495,659 US201213495659A US2012254315A1 US 20120254315 A1 US20120254315 A1 US 20120254315A1 US 201213495659 A US201213495659 A US 201213495659A US 2012254315 A1 US2012254315 A1 US 2012254315A1
- Authority
- US
- United States
- Prior art keywords
- client
- document
- transition
- cache
- metadata
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Definitions
- some computer applications allow multiple clients to simultaneously edit a document.
- a server may maintain a copy of the document.
- the server may need to continually update the copy of the document to reflect the current state of the document. This can lead to inefficiencies.
- the client's application may need to continuously update the server to allow the transition to multi-party editing when it occurs. This can increase server load, thereby causing a degradation in performance.
- Example systems and methods described herein relate to a caching infrastructure.
- an example method for retrieval of presence metadata includes: receiving a request from a first client to edit a document file; sending short-term check out metadata to the first client to begin an editing session; and writing the transition ID to a transition table stored in a cache, wherein the presence of another transition ID in the cache indicates that a document has switched from a single-client mode to a multi-client mode.
- an example system includes a cache infrastructure for retrieval of presence metadata.
- the system includes a memory storage unit, and a processing unit coupled to the memory storage unit, wherein the processing unit is operative to receive short-term check out metadata from a first client to begin an editing session, add a transition ID to the short-term check out metadata, write the transition ID to a transition table stored in a cache, and switch from a single-client mode to a multi-client mode. Switching from the single-client mode to the multi-client mode comprises the processing unit being operative to notice when the first client attempts to take another short-term lock on the document and seeing that that a second client has already received the document.
- the processing unit is operative to determine if the multi-client mode is in progress by checking a database, receive a ping from the first client to determine if the transition ID is in the cache, and when the transition ID is not in the cache, receive pings from the first client at regular intervals, and save the document to the server a plurality of times without incurring any reads/writes to the database, and, when the transition ID is in the cache, receive a ping from the first client to collect a lock table from the database to identify the second client, and receive the second client's lock information by receiving pings that do not carry lock information.
- an example client computer for retrieval of metadata relating to a multi-client editing session includes a memory unit, and a processing unit operative to receive a document from a storage device, the document comprising short-term check out metadata indicating an editing session has begun, ping a cache to determine if another transition ID is stored in the cache, and send a transition ID to a transition table stored in a cache when the another transition ID is not stored in the cache to switch from a single-client mode to a multi-client mode when the another transition ID is stored in the cache.
- FIG. 1 is a schematic block diagram illustrating an example authoring system
- FIG. 2 is a schematic block diagram illustrating the authoring system of FIG. 1 in which a document stored on first computing device can include content and metadata;
- FIG. 3 is a schematic block diagram of an example lock table
- FIG. 4 is a schematic block diagram of an example authoring environment including a first computing device on which a master copy of a document to be authored is to be stored;
- FIG. 5 is a schematic block diagram of an example client computing system configured to implement an authoring environment
- FIG. 6 is a flowchart illustrating an example caching process implemented by an authoring application to recognizes a single or multiple clients editing a document
- FIG. 7 is a flowchart of an example subroutine used in the method of FIG. 6 for writing a transition ID to a transition table.
- Embodiments of the present disclosure provide an environment in which multiple clients can collaboratively author a document while consuming minimal server resources.
- a coauthoring capable application when a coauthoring capable application is editing a document, the application adds coauthoring metadata to the document and keeps a server copy of the file updated with the latest metadata.
- the coauthoring metadata and server copy allows seamlessly transitions from a single client to a multi-client editing state and vice versa.
- the coauthoring metadata is uploaded to the server. When a new client opens the document, the client is notified of the areas of the document where other clients are working.
- FIG. 1 illustrates an example authoring system 100 having features that illustrate examples aspects of the disclosure.
- the authoring system 100 includes a storage device 120 storing a master copy of a document 150 .
- the storage device 120 may include, but not limited to, a server, a client computer, or other computing device.
- the storage device 120 can include one or more storage devices (e.g., a network of computing devices).
- the authoring system 100 also includes at least one client computing device 110 that is communicatively coupled to the storage device 120 .
- Each of the client computing devices 110 can edit the document 150 by creating a client copy 155 of the document 150 and editing the client copy 155 .
- the client copies 155 of the document 150 are synchronized when the client computing devices 110 periodically send to the storage device 120 updates to be shared with the other client computing devices and periodically obtain from the storage device 120 updates from other client computing devices.
- a client computing device 110 includes any computing device that obtains a client copy of a document to be authored from a master copy of the document.
- the client computing device 110 can be different from the storage device 120 or can include a different client account implemented on the storage device 120 .
- a computing device that acts as a storage device 120 for one document may act as a client computing device 110 for a different document and vice versa.
- each client computing device 110 A, 110 B, 110 C, 110 D can send to the storage device 120 updates generated by the client of the client computing device and can request from the storage device 120 updates generated by the clients of the other client computing devices.
- the storage device 120 can be a server computing device and the client computing devices 110 A, 110 B, 110 C, 110 D can be client computing devices.
- Other system configurations are possible.
- multiple server computing devices can be used.
- the document 150 stored on the storage device 120 can include content 152 and metadata 154 .
- Authoring applications 130 on the client computing devices 110 process and manipulate the content and metadata of the client copies 155 of the document 150 .
- metadata 154 can be stored separately from content 152 .
- content 152 can be stored in the document 150 and metadata 154 can be stored in a table (see FIG. 3 ) separate from the document 150 .
- the metadata 154 can be stored within the document 150 .
- the client computing devices 110 can synchronize updates to the content 152 separately from updates to the metadata 154 .
- metadata updates 154 are automatically synchronized among the storage device 120 and client computing devices 110 , whereas content updates 152 from each client computing device 110 are synchronized at the request of the respective client.
- lock metadata can be stored in a variety of different formats.
- the lock metadata of FIG. 3 is stored in a table format 300 .
- the lock table 300 of FIG. 3 includes a list of clients, each of whom is identified with a client identifier (e.g., an identification number) that is uniquely assigned to the client.
- Data units to be locked are identified with unit identifiers (e.g., identification numbers) that are uniquely assigned to each data unit within a document.
- the lock table 300 associates the unit identifiers of the one or more data units to be locked with the client identifiers of the clients who own the locks.
- data units 312 and 314 are associated with a first client 310 . Other clients, therefore, are inhibited from editing data units 312 and 314 .
- Data unit 322 is associated with client 320 . Other clients, including the first client 310 , therefore, are inhibited from editing data unit 322 .
- the fourth client 340 has not locked any portion of the document and so is not associated with any unit identifiers. In other embodiments, however, lock metadata can be stored in a different format or within the document.
- the lock table 300 can be arranged by unit identifier instead of by client identifier.
- Presence metadata also can be stored in a variety of formats. For example, presence metadata can be stored in the lock table 300 of FIG. 3 . In another embodiment, however, presence metadata can be stored in a separate table or in a different format. Presence metadata includes the client identifier of each client that is currently accessing the document or that has staked a claim (e.g., generated a content lock) on a data unit of the document. For example, a metadata table, such as the lock table 300 , can store the client identifier of each client having a claim to at least one data unit of the document. Like lock metadata, presence metadata can be synchronized automatically.
- FIGS. 4 and 5 provide greater detail in how coauthoring between the client copy and the master copy of the document is implemented by a client computing device.
- FIG. 4 is a schematic block diagram of an authoring system 400 including a storage device 420 on which a master copy of a document to be authored is to be stored.
- the authoring system 400 also includes at least one client computing device 410 communicatively coupled to the storage device 420 .
- the client computing device 410 includes an authoring application 412 configured to provide an authoring environment in which a client can create and/or manipulate a document to be authored.
- the client computing device 410 also includes a cache 414 , a layer object (“LO”) 416 , and a synchronization manager (“sync manager”) 418 .
- the cache 414 stores a client copy of the document to be authored.
- the cache 414 also stores the metadata, including lock and presence metadata, associated with the document. Updates to the content and metadata of the document also can be stored in the cache 414 .
- the layer object 416 provides an interface between the authoring application 412 and the cache 414 .
- the layer object 416 also provides an interface between the authoring application 412 and the sync manager 418 .
- the sync manager 418 communicates with the storage device 420 and provides an interface between the storage device 420 and the cache 414 .
- the sync manager 418 can send updates to and obtain updates from the storage device 420 and the cache 414 .
- an authoring environment having features that are examples of aspects in accordance with the principles of the disclosure can be implemented on a client computing device (e.g., a personal computer, a server computer, a notebook computer, a PDA, a Smartphone, or any other such computing device).
- a client computing device e.g., a personal computer, a server computer, a notebook computer, a PDA, a Smartphone, or any other such computing device.
- a non-limiting embodiment of a client computing system 500 configured to implement an authoring environment is described herein with reference to FIG. 5 .
- the exemplary computing system 500 for implementing the principles of the disclosure includes a client computing device, such as client computing device 510 .
- the client computing device 510 typically includes at least one processing unit 515 for executing applications and programs stored in system memory 520 .
- the system memory 520 may include, but is not limited to, RAM, ROM, EEPROM, flash memory, CD-ROM, digital versatile disks (DVD) or other optical storage devices, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other memory technology.
- System memory 520 typically stores an operating system 522 , such as the WINDOWS® operating systems from Microsoft Corporation of Redmond, Wash., suitable for controlling the operation of the computing device 510 .
- System memory 520 also may include a document cache 526 in which a client copy 527 of a document can be stored. Metadata 529 of the document also can be stored within the client cache 526 .
- the system memory 520 also may store one or more software applications, such as authoring applications 524 for creating and editing documents.
- authoring applications 524 suitable for authoring documents in accordance with the principles of the present disclosure is Word word processing software from Microsoft Corporation.
- Other non-limiting examples of authoring applications include POWERPOINT® presentation software and VISIO® drawing and diagramming software, both also from Microsoft Corporation.
- Other software applications can also be used.
- Computing device 510 also may have input device(s) 530 , such as a keyboard, mouse, pen, voice input device, touch input device, etc., for entering and manipulating data.
- input device(s) 530 such as a keyboard, mouse, pen, voice input device, touch input device, etc.
- Output device(s) 535 such as a display screen, speakers, printer, etc., also may be included. These output devices 535 are well known in the art and need not be discussed at length herein.
- the computing device 510 also may contain communication connections 540 that allow the device 510 to communicate with other computing devices, for example, the storage device 420 of FIG. 4 , over a network in a distributed computing environment (e.g., an intranet or the Internet).
- communication device media 540 includes wired media such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared and other wireless media.
- FIG. 6 is a flow chart setting forth the general stages involved in a method 600 consistent with an embodiment of the disclosure for retrieving presence metadata.
- Method 600 may be implemented using a computing device 510 as described in above with respect to FIG. 5 . Ways to implement the stages of method 600 will be described in greater detail below.
- Method 600 may begin at starting block 605 and proceed to stage 610 where computing device 510 may receive metadata 529 .
- computing device 510 may receive metadata 529 .
- a client using computing device 510 e.g. a client computer
- method 600 may advance to stage 620 where computing device 510 may add a transition ID to the metadata 529 .
- method 600 may continue to subroutine 630 where computing device 510 may write the transition ID to a transition table stored in cache 526 .
- writing the transition ID to metadata 529 may indicate more than one client is editing the document (i.e. switching from a single-client mode to a multi-client mode) as show in FIG. 7 .
- the transition ID is a unique number, such as a Globally Unique Identifier (GUID—i.e., a pseudo-random 128-bit number).
- GUID Globally Unique Identifier
- the transition table is a list of the transition IDs.
- the transition table can also include an expiration date for each transition ID. The expiration date can be used to clear a transition ID when a client forces creation of a transition ID and thereupon abandon editing of the document without notification. Other configurations are possible.
- method 600 may advance to stage 640 where computing device 510 may ping storage device 120 (e.g. a server) to determine if the transition ID is in cache 526 .
- storage device 120 e.g. a server
- computing device 510 may ping the server at regular intervals, and save the document to the server a plurality of times without incurring any reads/writes to a database that stores presence information.
- computing device 510 may ping the server to collect a lock table from a database to identify a new client, and in a separate web service request, submitting the client's lock information. Computing device 510 may then delete the transition ID from the transition table.
- Computing device 510 may also submit a client's lock information. Submitting the client's lock information may include pinging the server. For example, the computing device can submit “am I alone” pings to the server, wherein the “am I alone” pings do not carry lock information. An “am I alone” ping is simply a ping to the server or other storage device wherein computing device 510 is requesting information to determine if the document is being edit by another client or if another client had begun editing the document after the client began editing the document.
- each client downloads presence metadata Every time each client downloads presence metadata, the number of clients in an editing session and the last time each client updated their presence information (e.g., transition ID, transition table, database, etc.) may be checked (among other things), at regular intervals. If the presence information has not been updated by any client in a configurable window of time, it is considered a violent exit from the session. Any client who first observes this exit can delete the client from the presence information. Further, the delete operation should be a graceful merge so that any other client who also made the same observation can re-request the omissions which results in a no-op in the server.
- presence information e.g., transition ID, transition table, database, etc.
- the presence information reflects only one client (which should be the examining client, i.e., computing device 510 ) the following actions may be done to minimize problems associated with the timing of the change of state of the document: 1) clear-up the presence table so it reflects the state as a single client mode; 2) delete the transition ID to the transition table; and 3) start the “am I alone” pings at regular intervals.
- the transition ID in the transition table indicates another user has joined the coauthoring session and is in transition back to multi-user authoring.
- that client starts sending the “am I alone” pings.
- the “am I alone” pings returned to the client indicate the client is alone until another client puts the transition ID back in the transition table.
- method 600 may continue to stage 650 where computing device 510 may refresh cache 526 .
- computing device 510 may refresh cache 526 by updating the transition table stored in cache 526 .
- updating the transition table may include pinging cache 526 to check for the presence of the transition ID in cache 526 .
- a determination may be made to see if cache 526 has been refreshed within a predetermined time interval.
- a response to the ping may be sent from cache 526 .
- the transition table corresponding to the document's content database may be fetched.
- FIG. 7 is a flow chart showing example stages of subroutine 630 .
- Subroutine 630 begins at starting block 705 and proceeds to stage 710 where computing device 510 may determine if the document is already being used in the multi-client mode. For example, computing device 510 may determine if the document is in multi-client mode by checking a database. If computing device 510 determines the document is not in multi-client mode in stage 710 , subroutine 630 may proceed to stage 715 where computing device 510 switch from a single-client mode to a multi-client mode.
- switching from single-client mode to multi-client mode may be initiated by a second client attempting to take another short-term lock on the document and seeing that that the client has already received the document.
- Switching to multi-client mode may include computing device 510 receiving the document and transition ID at cache 526 .
- computing device 510 may actually be a second client computing device.
- computing device 510 may write the transition ID to the transition table, and write to the database information indicating the second client has joined the editing session and is now working on the document.
- subroutine 630 may continue to stage 720 where computing device 510 may adds the client as the “nth” client.
- adding the “nth” client may include computing device 510 receiving the document and transition ID, and writing to the database information indicating the “nth” client has joined the editing session.
- subroutine 630 may advance to stage 730 where computing device 510 may return to stage 640 ( FIG. 6 ).
- the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments or aspects.
- reference to a single item may mean a single item or a plurality of items, just as reference to a plurality of items may mean a single item.
- use of the term “and” when incorporated into a list is intended to imply that all the elements of the list, a single item of the list, or any combination of items in the list has been contemplated.
- Embodiments of the disclosure may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media.
- the processes (programs) can be implemented in any number of ways, including the structures described in this document. One such way is by machine operations, of devices of the type described in this document. Another optional way is for one or more of the individual operations of the methods to be performed on a computing device in conjunction with one or more human operators performing some of the operations. These human operators need not be collocated with each other, but each can be only with a machine that performs a portion of the program.
- the computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.
- the computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process.
- the term computer readable media as used herein includes both storage media and communication media.
- the disclosure may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- the disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote memory storage devices.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
Abstract
Example systems and methods are directed at maintaining and retrieving presence metadata. One example method includes receiving a request from a first client to edit a document file, and sending short-term check out metadata to the first client to begin an editing session. The method also includes writing the transition ID to a transition table stored in a cache, wherein the presence of another transition ID in the cache indicates that a document has switched from a single-client mode to a multi-client mode. An example system includes a processing unit operative to receive a document, the document including short-term check out metadata indicating an editing session has begun, ping a cache to determine if another transition ID is stored in the cache, and send a transition ID to a transition table stored in a cache to switch from a single-client mode to a multi-client mode.
Description
- In a collaborative environment, some computer applications allow multiple clients to simultaneously edit a document. As multiple clients are editing the document, a server may maintain a copy of the document. The server may need to continually update the copy of the document to reflect the current state of the document. This can lead to inefficiencies.
- For example, even with only a single client editing the document, the client's application may need to continuously update the server to allow the transition to multi-party editing when it occurs. This can increase server load, thereby causing a degradation in performance.
- Example systems and methods described herein relate to a caching infrastructure.
- According to one aspect, an example method for retrieval of presence metadata includes: receiving a request from a first client to edit a document file; sending short-term check out metadata to the first client to begin an editing session; and writing the transition ID to a transition table stored in a cache, wherein the presence of another transition ID in the cache indicates that a document has switched from a single-client mode to a multi-client mode.
- According to another aspect, an example system includes a cache infrastructure for retrieval of presence metadata. The system includes a memory storage unit, and a processing unit coupled to the memory storage unit, wherein the processing unit is operative to receive short-term check out metadata from a first client to begin an editing session, add a transition ID to the short-term check out metadata, write the transition ID to a transition table stored in a cache, and switch from a single-client mode to a multi-client mode. Switching from the single-client mode to the multi-client mode comprises the processing unit being operative to notice when the first client attempts to take another short-term lock on the document and seeing that that a second client has already received the document. The processing unit is operative to determine if the multi-client mode is in progress by checking a database, receive a ping from the first client to determine if the transition ID is in the cache, and when the transition ID is not in the cache, receive pings from the first client at regular intervals, and save the document to the server a plurality of times without incurring any reads/writes to the database, and, when the transition ID is in the cache, receive a ping from the first client to collect a lock table from the database to identify the second client, and receive the second client's lock information by receiving pings that do not carry lock information.
- According to yet another aspect, an example client computer for retrieval of metadata relating to a multi-client editing session includes a memory unit, and a processing unit operative to receive a document from a storage device, the document comprising short-term check out metadata indicating an editing session has begun, ping a cache to determine if another transition ID is stored in the cache, and send a transition ID to a transition table stored in a cache when the another transition ID is not stored in the cache to switch from a single-client mode to a multi-client mode when the another transition ID is stored in the cache.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter. Nor is this Summary intended to be used to limit the claimed subject matter's scope.
- Non-limiting and non-exhaustive embodiments are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified.
-
FIG. 1 is a schematic block diagram illustrating an example authoring system; -
FIG. 2 is a schematic block diagram illustrating the authoring system ofFIG. 1 in which a document stored on first computing device can include content and metadata; -
FIG. 3 is a schematic block diagram of an example lock table; -
FIG. 4 is a schematic block diagram of an example authoring environment including a first computing device on which a master copy of a document to be authored is to be stored; -
FIG. 5 is a schematic block diagram of an example client computing system configured to implement an authoring environment; -
FIG. 6 is a flowchart illustrating an example caching process implemented by an authoring application to recognizes a single or multiple clients editing a document; and -
FIG. 7 is a flowchart of an example subroutine used in the method ofFIG. 6 for writing a transition ID to a transition table. - In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. While the disclosure will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computer system, those skilled in the art will recognize that the disclosure also may be implemented in combination with other program modules. The embodiments described herein may be combined and other embodiments may be utilized without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the disclosure is defined by the appended claims and their equivalents.
- Embodiments of the present disclosure provide an environment in which multiple clients can collaboratively author a document while consuming minimal server resources. In example embodiments, when a coauthoring capable application is editing a document, the application adds coauthoring metadata to the document and keeps a server copy of the file updated with the latest metadata. The coauthoring metadata and server copy allows seamlessly transitions from a single client to a multi-client editing state and vice versa. To keep conflicts to a minimum, the coauthoring metadata is uploaded to the server. When a new client opens the document, the client is notified of the areas of the document where other clients are working.
-
FIG. 1 illustrates anexample authoring system 100 having features that illustrate examples aspects of the disclosure. Theauthoring system 100 includes astorage device 120 storing a master copy of adocument 150. In one embodiment, thestorage device 120 may include, but not limited to, a server, a client computer, or other computing device. In another embodiment, thestorage device 120 can include one or more storage devices (e.g., a network of computing devices). - The
authoring system 100 also includes at least one client computing device 110 that is communicatively coupled to thestorage device 120. Each of the client computing devices 110 can edit thedocument 150 by creating a client copy 155 of thedocument 150 and editing the client copy 155. The client copies 155 of thedocument 150 are synchronized when the client computing devices 110 periodically send to thestorage device 120 updates to be shared with the other client computing devices and periodically obtain from thestorage device 120 updates from other client computing devices. - As the term is used herein, a client computing device 110 includes any computing device that obtains a client copy of a document to be authored from a master copy of the document. The client computing device 110 can be different from the
storage device 120 or can include a different client account implemented on thestorage device 120. In one embodiment, a computing device that acts as astorage device 120 for one document may act as a client computing device 110 for a different document and vice versa. - In the example shown, four
client computing devices storage device 120. In other embodiments, however, any number of computing devices 110 may be coupled to thestorage device 120. In the example shown, eachclient computing device storage device 120 updates generated by the client of the client computing device and can request from thestorage device 120 updates generated by the clients of the other client computing devices. In one embodiment, thestorage device 120 can be a server computing device and theclient computing devices - As shown in
FIG. 2 , thedocument 150 stored on thestorage device 120 can includecontent 152 andmetadata 154. Authoringapplications 130 on the client computing devices 110 process and manipulate the content and metadata of the client copies 155 of thedocument 150. In some embodiments,metadata 154 can be stored separately fromcontent 152. For example,content 152 can be stored in thedocument 150 andmetadata 154 can be stored in a table (seeFIG. 3 ) separate from thedocument 150. In other embodiments, however, themetadata 154 can be stored within thedocument 150. - In general, the client computing devices 110 can synchronize updates to the
content 152 separately from updates to themetadata 154. In general,metadata updates 154 are automatically synchronized among thestorage device 120 and client computing devices 110, whereascontent updates 152 from each client computing device 110 are synchronized at the request of the respective client. - Referring to
FIG. 3 , lock metadata can be stored in a variety of different formats. For example, the lock metadata ofFIG. 3 is stored in a table format 300. The lock table 300 ofFIG. 3 includes a list of clients, each of whom is identified with a client identifier (e.g., an identification number) that is uniquely assigned to the client. Data units to be locked are identified with unit identifiers (e.g., identification numbers) that are uniquely assigned to each data unit within a document. The lock table 300 associates the unit identifiers of the one or more data units to be locked with the client identifiers of the clients who own the locks. - For example, in the lock table 300, data units 312 and 314 are associated with a first client 310. Other clients, therefore, are inhibited from editing data units 312 and 314. Data unit 322 is associated with client 320. Other clients, including the first client 310, therefore, are inhibited from editing data unit 322. The fourth client 340 has not locked any portion of the document and so is not associated with any unit identifiers. In other embodiments, however, lock metadata can be stored in a different format or within the document. For example, the lock table 300 can be arranged by unit identifier instead of by client identifier.
- Presence metadata also can be stored in a variety of formats. For example, presence metadata can be stored in the lock table 300 of
FIG. 3 . In another embodiment, however, presence metadata can be stored in a separate table or in a different format. Presence metadata includes the client identifier of each client that is currently accessing the document or that has staked a claim (e.g., generated a content lock) on a data unit of the document. For example, a metadata table, such as the lock table 300, can store the client identifier of each client having a claim to at least one data unit of the document. Like lock metadata, presence metadata can be synchronized automatically. -
FIGS. 4 and 5 provide greater detail in how coauthoring between the client copy and the master copy of the document is implemented by a client computing device.FIG. 4 is a schematic block diagram of anauthoring system 400 including astorage device 420 on which a master copy of a document to be authored is to be stored. Theauthoring system 400 also includes at least oneclient computing device 410 communicatively coupled to thestorage device 420. - The
client computing device 410 includes anauthoring application 412 configured to provide an authoring environment in which a client can create and/or manipulate a document to be authored. Theclient computing device 410 also includes acache 414, a layer object (“LO”) 416, and a synchronization manager (“sync manager”) 418. Thecache 414 stores a client copy of the document to be authored. Thecache 414 also stores the metadata, including lock and presence metadata, associated with the document. Updates to the content and metadata of the document also can be stored in thecache 414. - The
layer object 416 provides an interface between theauthoring application 412 and thecache 414. Thelayer object 416 also provides an interface between theauthoring application 412 and thesync manager 418. Thesync manager 418 communicates with thestorage device 420 and provides an interface between thestorage device 420 and thecache 414. For example, thesync manager 418 can send updates to and obtain updates from thestorage device 420 and thecache 414. - In general, an authoring environment having features that are examples of aspects in accordance with the principles of the disclosure can be implemented on a client computing device (e.g., a personal computer, a server computer, a notebook computer, a PDA, a Smartphone, or any other such computing device). A non-limiting embodiment of a
client computing system 500 configured to implement an authoring environment is described herein with reference toFIG. 5 . - In
FIG. 5 , theexemplary computing system 500 for implementing the principles of the disclosure includes a client computing device, such asclient computing device 510. In a basic configuration, theclient computing device 510 typically includes at least oneprocessing unit 515 for executing applications and programs stored insystem memory 520. Depending on the exact configuration and type ofcomputing device 510, thesystem memory 520 may include, but is not limited to, RAM, ROM, EEPROM, flash memory, CD-ROM, digital versatile disks (DVD) or other optical storage devices, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other memory technology. -
System memory 520 typically stores anoperating system 522, such as the WINDOWS® operating systems from Microsoft Corporation of Redmond, Wash., suitable for controlling the operation of thecomputing device 510.System memory 520 also may include adocument cache 526 in which aclient copy 527 of a document can be stored.Metadata 529 of the document also can be stored within theclient cache 526. - The
system memory 520 also may store one or more software applications, such asauthoring applications 524 for creating and editing documents. One non-limiting example of anauthoring application 524 suitable for authoring documents in accordance with the principles of the present disclosure is Word word processing software from Microsoft Corporation. Other non-limiting examples of authoring applications include POWERPOINT® presentation software and VISIO® drawing and diagramming software, both also from Microsoft Corporation. Other software applications can also be used. -
Computing device 510 also may have input device(s) 530, such as a keyboard, mouse, pen, voice input device, touch input device, etc., for entering and manipulating data. Output device(s) 535, such as a display screen, speakers, printer, etc., also may be included. Theseoutput devices 535 are well known in the art and need not be discussed at length herein. - The
computing device 510 also may containcommunication connections 540 that allow thedevice 510 to communicate with other computing devices, for example, thestorage device 420 ofFIG. 4 , over a network in a distributed computing environment (e.g., an intranet or the Internet). By way of example, and not limitation,communication device media 540 includes wired media such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared and other wireless media. - Turning now to
FIG. 6 is a flow chart setting forth the general stages involved in amethod 600 consistent with an embodiment of the disclosure for retrieving presence metadata.Method 600 may be implemented using acomputing device 510 as described in above with respect toFIG. 5 . Ways to implement the stages ofmethod 600 will be described in greater detail below.Method 600 may begin at startingblock 605 and proceed to stage 610 wherecomputing device 510 may receivemetadata 529. For example, a client using computing device 510 (e.g. a client computer) may open a document (e.g. 150). Opening the document may causecomputing device 510 to receive short-term check out metadata for the document. - From
stage 610, wherecomputing device 510 receivedmetadata 529,method 600 may advance to stage 620 wherecomputing device 510 may add a transition ID to themetadata 529. - Once
computing device 510 adds the transition ID tometadata 529 instage 620,method 600 may continue to subroutine 630 wherecomputing device 510 may write the transition ID to a transition table stored incache 526. For example, writing the transition ID to metadata 529 may indicate more than one client is editing the document (i.e. switching from a single-client mode to a multi-client mode) as show inFIG. 7 . - In one example, the transition ID is a unique number, such as a Globally Unique Identifier (GUID—i.e., a pseudo-random 128-bit number). The transition table is a list of the transition IDs. The transition table can also include an expiration date for each transition ID. The expiration date can be used to clear a transition ID when a client forces creation of a transition ID and thereupon abandon editing of the document without notification. Other configurations are possible.
- From
subroutine stage 630, wherecomputing device 510 may write the transition ID to a transition table stored incache 526,method 600 may advance to stage 640 wherecomputing device 510 may ping storage device 120 (e.g. a server) to determine if the transition ID is incache 526. - When the transition ID is not in the cache,
computing device 510 may ping the server at regular intervals, and save the document to the server a plurality of times without incurring any reads/writes to a database that stores presence information. - When the transition ID is in the cache,
computing device 510 may ping the server to collect a lock table from a database to identify a new client, and in a separate web service request, submitting the client's lock information.Computing device 510 may then delete the transition ID from the transition table. -
Computing device 510 may also submit a client's lock information. Submitting the client's lock information may include pinging the server. For example, the computing device can submit “am I alone” pings to the server, wherein the “am I alone” pings do not carry lock information. An “am I alone” ping is simply a ping to the server or other storage device whereincomputing device 510 is requesting information to determine if the document is being edit by another client or if another client had begun editing the document after the client began editing the document. - Every time each client downloads presence metadata, the number of clients in an editing session and the last time each client updated their presence information (e.g., transition ID, transition table, database, etc.) may be checked (among other things), at regular intervals. If the presence information has not been updated by any client in a configurable window of time, it is considered a violent exit from the session. Any client who first observes this exit can delete the client from the presence information. Further, the delete operation should be a graceful merge so that any other client who also made the same observation can re-request the omissions which results in a no-op in the server.
- If the presence information reflects only one client (which should be the examining client, i.e., computing device 510), the following actions may be done to minimize problems associated with the timing of the change of state of the document: 1) clear-up the presence table so it reflects the state as a single client mode; 2) delete the transition ID to the transition table; and 3) start the “am I alone” pings at regular intervals.
- The transition ID in the transition table indicates another user has joined the coauthoring session and is in transition back to multi-user authoring. When the system transitions back to one client editing, that client starts sending the “am I alone” pings. The “am I alone” pings returned to the client indicate the client is alone until another client puts the transition ID back in the transition table.
- Once
computing device 510pings storage device 120 instage 640,method 600 may continue to stage 650 wherecomputing device 510 may refreshcache 526. - For example,
computing device 510 may refreshcache 526 by updating the transition table stored incache 526. For instance updating the transition table may include pingingcache 526 to check for the presence of the transition ID incache 526. When the transition ID is not present incache 526, a determination may be made to see ifcache 526 has been refreshed within a predetermined time interval. Whencache 526 has been refreshed within the predetermined time interval, a response to the ping may be sent fromcache 526. Whencache 526 has not been refreshed within the predetermined time interval, the transition table corresponding to the document's content database may be fetched. Oncecomputing device 510 hasrefresh cache 526 instage 650,method 600 may then end atstage 660. -
FIG. 7 is a flow chart showing example stages ofsubroutine 630.Subroutine 630 begins at startingblock 705 and proceeds to stage 710 wherecomputing device 510 may determine if the document is already being used in the multi-client mode. For example,computing device 510 may determine if the document is in multi-client mode by checking a database. Ifcomputing device 510 determines the document is not in multi-client mode instage 710,subroutine 630 may proceed to stage 715 wherecomputing device 510 switch from a single-client mode to a multi-client mode. - For example, switching from single-client mode to multi-client mode may be initiated by a second client attempting to take another short-term lock on the document and seeing that that the client has already received the document. Switching to multi-client mode may include
computing device 510 receiving the document and transition ID atcache 526. In thisinstance computing device 510 may actually be a second client computing device. After receiving the transition ID,computing device 510 may write the transition ID to the transition table, and write to the database information indicating the second client has joined the editing session and is now working on the document. - If
computing device 510 determines the document is in multi-client mode instage 710,subroutine 630 may continue to stage 720 wherecomputing device 510 may adds the client as the “nth” client. For example, adding the “nth” client may includecomputing device 510 receiving the document and transition ID, and writing to the database information indicating the “nth” client has joined the editing session. - From
stage 715 wherecomputing device 510 switches from single-client mode to multi-client mode orstage 720 wherecomputing device 510 adds the “nth” client,subroutine 630 may advance to stage 730 wherecomputing device 510 may return to stage 640 (FIG. 6 ). - Reference may be made throughout this specification to “one embodiment,” “an embodiment,” “embodiments,” “an aspect,” or “aspects” meaning that a particular described feature, structure, or characteristic may be included in at least one embodiment of the present disclosure. Thus, usage of such phrases may refer to more than just one embodiment or aspect. In addition, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments or aspects. Furthermore, reference to a single item may mean a single item or a plurality of items, just as reference to a plurality of items may mean a single item. Moreover, use of the term “and” when incorporated into a list is intended to imply that all the elements of the list, a single item of the list, or any combination of items in the list has been contemplated.
- Embodiments of the disclosure may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The processes (programs) can be implemented in any number of ways, including the structures described in this document. One such way is by machine operations, of devices of the type described in this document. Another optional way is for one or more of the individual operations of the methods to be performed on a computing device in conjunction with one or more human operators performing some of the operations. These human operators need not be collocated with each other, but each can be only with a machine that performs a portion of the program.
- The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. The term computer readable media as used herein includes both storage media and communication media.
- Those skilled in the art will appreciate that the disclosure may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
Claims (21)
1-20. (canceled)
21. A method for updating presence information for a document, the method comprising:
receiving, at a first client, short term check out metadata by opening the document, the short term check out metadata comprising presence metadata;
adding a transition ID for the first client to the short term check out metadata;
sending the transition ID to a transition table stored in a cache;
determining that presence information in the cache has not been updated by a second client in a configurable window of time; and
upon determining that the presence information has not been updated, deleting the presence information of the second client.
22. The method of claim 21 , wherein adding the transition ID for the first client switches the document to a multi client editing mode.
23. The method of claim 21 , wherein deleting the presence information of the second client indicates that the document is in a single client editing mode.
24. The method of claim 21 , further comprising:
deleting the transition ID from the transition table.
25. The method of claim 21 , further comprising:
pinging the server to determine whether a new transition ID has been added to the transition table.
26. The method of claim 25 , further comprising
receiving a ping from the server indicating that the document is still in the single client editing mode.
27. The method of claim 25 , further comprising
receiving a ping from the server indicating that the document has switched to the multi client editing mode.
28. One or more computer storage media not consisting of a propagated data signal and having computer-executable instructions that, when executed, provide a method for updating presence information for a document, the method comprising:
receiving, at a first client, short term check out metadata by opening the document, the short term check out metadata comprising presence metadata;
adding a transition ID for the first client to the short term check out metadata;
sending the transition ID to a transition table stored in a cache;
determining that presence information in the cache has not been updated by a second client in a configurable window of time; and
upon determining that the presence information has not been updated, deleting the presence information of the second client.
29. The one or more computer storage media of claim 28 , wherein adding the transition ID for the first client switches the document to a multi client editing mode.
30. The one or more computer storage media of claim 28 , wherein deleting the presence information of the second client indicates that the document is in a single client editing mode.
31. The one or more computer storage media of claim 28 , further comprising:
deleting the transition ID from the transition table.
32. The one or more computer storage media of claim 28 , further comprising:
pinging the server to determine whether a new transition ID has been added to the transition table.
33. The one or more computer storage media of claim 32 , further comprising
receiving a ping from the server indicating that the document is still in the single client editing mode.
34. The one or more computer storage media of claim 32 , further comprising
receiving a ping from the server indicating that the document has switched to the multi client editing mode.
35. A computer system comprising:
a processor; and
a memory communicatively coupled to the processor, the memory having computer-executable instructions that when executed by the processor, provide a method for updating presence information for a document, the method comprising:
receiving, at a first client, short term check out metadata by opening the document, the short term check out metadata comprising presence metadata;
adding a transition ID for the first client to the short term check out metadata;
sending the transition ID to a transition table stored in a cache;
determining that presence information in the cache has not been updated by a second client in a configurable window of time; and
upon determining that the presence information has not been updated, deleting the presence information of the second client.
36. The computer system of claim 35 , wherein adding the transition ID for the first client switches the document to a multi client editing mode.
37. The computer system of claim 35 , wherein deleting the presence information of the second client indicates that the document is in a single client editing mode.
38. The computer system of claim 35 , further comprising:
deleting the transition ID from the transition table.
39. The computer system of claim 35 , further comprising:
pinging the server to determine whether a new transition ID has been added to the transition table.
40. The computer system of claim 39 , further comprising
receiving a ping from the server indicating that the document has switched to the multi client editing mode.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/495,659 US20120254315A1 (en) | 2008-05-08 | 2012-06-13 | Caching infrastructure |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/117,025 US8825594B2 (en) | 2008-05-08 | 2008-05-08 | Caching infrastructure |
US13/495,659 US20120254315A1 (en) | 2008-05-08 | 2012-06-13 | Caching infrastructure |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/117,025 Continuation US8825594B2 (en) | 2008-05-08 | 2008-05-08 | Caching infrastructure |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120254315A1 true US20120254315A1 (en) | 2012-10-04 |
Family
ID=41267722
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/117,025 Active 2028-09-15 US8825594B2 (en) | 2008-05-08 | 2008-05-08 | Caching infrastructure |
US13/495,659 Abandoned US20120254315A1 (en) | 2008-05-08 | 2012-06-13 | Caching infrastructure |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/117,025 Active 2028-09-15 US8825594B2 (en) | 2008-05-08 | 2008-05-08 | Caching infrastructure |
Country Status (1)
Country | Link |
---|---|
US (2) | US8825594B2 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090271696A1 (en) * | 2008-04-28 | 2009-10-29 | Microsoft Corporation | Conflict Resolution |
US8346768B2 (en) | 2009-04-30 | 2013-01-01 | Microsoft Corporation | Fast merge support for legacy documents |
US8352418B2 (en) | 2007-11-09 | 2013-01-08 | Microsoft Corporation | Client side locking |
US8417666B2 (en) | 2008-06-25 | 2013-04-09 | Microsoft Corporation | Structured coauthoring |
US8429753B2 (en) | 2008-05-08 | 2013-04-23 | Microsoft Corporation | Controlling access to documents using file locks |
US8825758B2 (en) | 2007-12-14 | 2014-09-02 | Microsoft Corporation | Collaborative authoring modes |
US8825594B2 (en) | 2008-05-08 | 2014-09-02 | Microsoft Corporation | Caching infrastructure |
Families Citing this family (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5211557B2 (en) * | 2007-06-15 | 2013-06-12 | 富士通株式会社 | Web conference support program, recording medium recording the program, Web conference support device, and Web conference support method |
US8301588B2 (en) | 2008-03-07 | 2012-10-30 | Microsoft Corporation | Data storage for file updates |
GB2464948A (en) | 2008-10-29 | 2010-05-05 | Quolos Limited | Online collaboration |
US9063806B2 (en) * | 2009-01-29 | 2015-06-23 | Oracle International Corporation | Flex integration with a secure application |
US9659335B2 (en) | 2009-01-29 | 2017-05-23 | Oracle International Corporation | Sample management for a sales call |
US9684736B2 (en) * | 2009-01-29 | 2017-06-20 | Oracle International Corporation | Communication handler for flex integration with a secure application |
US9760381B2 (en) | 2009-01-30 | 2017-09-12 | Oracle International Corporation | Configurable toolbar |
US9396279B1 (en) | 2009-02-17 | 2016-07-19 | Jpmorgan Chase Bank, Na | Collaborative virtual markup |
US20110252125A1 (en) * | 2010-04-09 | 2011-10-13 | Microsoft Corporation | Dynamic Syncing |
US8892632B2 (en) | 2010-06-04 | 2014-11-18 | Microsoft Corporation | Client-server interaction frequency control |
US20120101980A1 (en) * | 2010-10-26 | 2012-04-26 | Microsoft Corporation | Synchronizing online document edits |
US10140420B2 (en) * | 2011-10-12 | 2018-11-27 | Merge Healthcare Incorporation | Systems and methods for independent assessment of image data |
US9460073B2 (en) * | 2013-02-27 | 2016-10-04 | Google Inc. | Systems and methods for mutations and operational transforms in a collaborative spreadsheet environment |
CN104182397B (en) * | 2013-05-21 | 2018-09-04 | 北大方正集团有限公司 | Document cooperative processing method, system and equipment |
US10325014B2 (en) | 2015-04-30 | 2019-06-18 | Workiva Inc. | System and method for convergent document collaboration |
US9292482B1 (en) | 2015-04-30 | 2016-03-22 | Workiva Inc. | System and method for convergent document collaboration |
US20160321226A1 (en) * | 2015-05-01 | 2016-11-03 | Microsoft Technology Licensing, Llc | Insertion of unsaved content via content channel |
US11677624B2 (en) * | 2019-04-12 | 2023-06-13 | Red Hat, Inc. | Configuration of a server in view of a number of clients connected to the server |
US11755825B2 (en) | 2019-09-12 | 2023-09-12 | Workiva Inc. | Method, system, and computing device for facilitating private drafting |
US11100281B1 (en) | 2020-08-17 | 2021-08-24 | Workiva Inc. | System and method for maintaining links and revisions |
US11443108B2 (en) | 2020-08-17 | 2022-09-13 | Workiva Inc. | System and method for document management using branching |
US11100277B1 (en) | 2021-02-15 | 2021-08-24 | Workiva Inc. | Systems, methods, and computer-readable media for flow-through formatting for links |
US11354362B1 (en) | 2021-05-06 | 2022-06-07 | Workiva Inc. | System and method for copying linked documents |
US11640495B1 (en) | 2021-10-15 | 2023-05-02 | Workiva Inc. | Systems and methods for translation comments flowback |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090125518A1 (en) * | 2007-11-09 | 2009-05-14 | Microsoft Corporation | Collaborative Authoring |
US20090157811A1 (en) * | 2007-12-14 | 2009-06-18 | Microsoft Corporation | Collaborative Authoring Modes |
Family Cites Families (283)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2004A (en) * | 1841-03-12 | Improvement in the manner of constructing and propelling steam-vessels | ||
US4855580A (en) | 1987-11-20 | 1989-08-08 | Recognition Equipment Incorporated | Data merge document processing method |
US5107443A (en) | 1988-09-07 | 1992-04-21 | Xerox Corporation | Private regions within a shared workspace |
US5799320A (en) | 1989-08-23 | 1998-08-25 | John R. Klug | Remote multiple-user editing system and method |
US5142619A (en) | 1990-02-21 | 1992-08-25 | International Business Machines Corporation | Method and apparatus for visually comparing files in a data processing system |
CA2039652C (en) | 1990-05-30 | 1996-12-24 | Frank Zdybel, Jr. | Hardcopy lossless data storage and communications for electronic document processing systems |
US5313394A (en) | 1990-12-11 | 1994-05-17 | Barbara Clapp | Document assembly customization system for modifying a source instrument including text and decisional commands |
US5671428A (en) | 1991-08-28 | 1997-09-23 | Kabushiki Kaisha Toshiba | Collaborative document processing system with version and comment management |
US5339389A (en) | 1991-12-31 | 1994-08-16 | International Business Machines Corporation | User selectable lock regions |
JPH0827754B2 (en) | 1992-05-21 | 1996-03-21 | インターナショナル・ビジネス・マシーンズ・コーポレイション | File management method and file management system in computer system |
JP3252454B2 (en) | 1992-06-30 | 2002-02-04 | 富士ゼロックス株式会社 | Shared data change status monitoring device |
US5555388A (en) | 1992-08-20 | 1996-09-10 | Borland International, Inc. | Multi-user system and methods providing improved file management by reading |
US5963931A (en) | 1992-10-05 | 1999-10-05 | Expert Systems Publishing Co. | Computer-assisted decision management system |
US5579223A (en) | 1992-12-24 | 1996-11-26 | Microsoft Corporation | Method and system for incorporating modifications made to a computer program into a translated version of the computer program |
US5446842A (en) | 1993-02-26 | 1995-08-29 | Taligent, Inc. | Object-oriented collaboration system |
JP2703498B2 (en) | 1993-04-30 | 1998-01-26 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Locking mechanism for versioned objects |
JP3053153B2 (en) | 1993-09-20 | 2000-06-19 | 株式会社日立製作所 | How to start application of document management system |
US6760840B1 (en) | 1994-03-15 | 2004-07-06 | Kabushiki Kaisha Toshiba | File editing system and shared file editing system with file content secrecy, file version management, and asynchronous editing |
US5831615A (en) | 1994-09-30 | 1998-11-03 | Intel Corporation | Method and apparatus for redrawing transparent windows |
US6181837B1 (en) | 1994-11-18 | 2001-01-30 | The Chase Manhattan Bank, N.A. | Electronic check image storage and retrieval system |
US5751958A (en) | 1995-06-30 | 1998-05-12 | Peoplesoft, Inc. | Allowing inconsistency in a distributed client-server application |
US5887146A (en) * | 1995-08-14 | 1999-03-23 | Data General Corporation | Symmetric multiprocessing computer with non-uniform memory access architecture |
US5729734A (en) | 1995-11-03 | 1998-03-17 | Apple Computer, Inc. | File privilege administration apparatus and methods |
US5781908A (en) | 1995-12-18 | 1998-07-14 | J.D. Edwards World Source Company | File data synchronizer in a distributed data computer network |
US6006239A (en) | 1996-03-15 | 1999-12-21 | Microsoft Corporation | Method and system for allowing multiple users to simultaneously edit a spreadsheet |
US5781732A (en) | 1996-06-20 | 1998-07-14 | Object Technology Licensing Corp. | Framework for constructing shared documents that can be collaboratively accessed by multiple users |
US5787262A (en) | 1996-06-26 | 1998-07-28 | Microsoft Corporation | System and method for distributed conflict resolution between data objects replicated across a computer network |
US5835950A (en) * | 1996-07-12 | 1998-11-10 | Samsung Electronics Co., Ltd. | Self-invalidation method for reducing coherence overheads in a bus-based shared-memory multiprocessor apparatus |
US6244575B1 (en) | 1996-10-02 | 2001-06-12 | Micron Technology, Inc. | Method and apparatus for vaporizing liquid precursors and system for using same |
US6202085B1 (en) | 1996-12-06 | 2001-03-13 | Microsoft Corportion | System and method for incremental change synchronization between multiple copies of data |
US6708221B1 (en) | 1996-12-13 | 2004-03-16 | Visto Corporation | System and method for globally and securely accessing unified information in a computer network |
US6065026A (en) | 1997-01-09 | 2000-05-16 | Document.Com, Inc. | Multi-user electronic document authoring system with prompted updating of shared language |
JP2996197B2 (en) | 1997-02-14 | 1999-12-27 | 日本電気株式会社 | Document sharing management method |
US6233600B1 (en) | 1997-07-15 | 2001-05-15 | Eroom Technology, Inc. | Method and system for providing a networked collaborative work environment |
US6209010B1 (en) | 1997-07-18 | 2001-03-27 | Varis Corporation | Computer implemented method for wrapping data to an arbitrary path defined by a page description language |
US6240414B1 (en) | 1997-09-28 | 2001-05-29 | Eisolutions, Inc. | Method of resolving data conflicts in a shared data environment |
US7447712B2 (en) | 1997-09-28 | 2008-11-04 | Global 360, Inc. | Structured workfolder |
US5946700A (en) | 1997-10-31 | 1999-08-31 | Oracle Corporation | Method and apparatus for preserving non-current information that can be overwritten in a computer file |
US6327611B1 (en) | 1997-11-12 | 2001-12-04 | Netscape Communications Corporation | Electronic document routing system |
US6067551A (en) | 1997-11-14 | 2000-05-23 | Microsoft Corporation | Computer implemented method for simultaneous multi-user editing of a document |
US6073161A (en) | 1997-12-16 | 2000-06-06 | International Business Machines Corporation | Method and apparatus for determining editing conflicts in a multi-authoring system |
US6000945A (en) | 1998-02-09 | 1999-12-14 | Educational Testing Service | System and method for computer based test assembly |
US6088702A (en) | 1998-02-25 | 2000-07-11 | Plantz; Scott H. | Group publishing system |
AUPP252298A0 (en) | 1998-03-24 | 1998-04-23 | 80-20 Software Pty Limited | Document management software |
US6275935B1 (en) | 1998-04-17 | 2001-08-14 | Thingworld.Com, Llc | Systems and methods for locking interactive objects |
US6209128B1 (en) | 1998-06-05 | 2001-03-27 | International Business Machines Corporation | Apparatus and method for providing access to multiple object versions |
US6438564B1 (en) | 1998-06-17 | 2002-08-20 | Microsoft Corporation | Method for associating a discussion with a document |
JP2000076109A (en) | 1998-08-28 | 2000-03-14 | Toshiba Corp | Data display device and data display method |
US6507845B1 (en) | 1998-09-14 | 2003-01-14 | International Business Machines Corporation | Method and software for supporting improved awareness of and collaboration among users involved in a task |
US6341291B1 (en) | 1998-09-28 | 2002-01-22 | Bentley Systems, Inc. | System for collaborative engineering using component and file-oriented tools |
US6324544B1 (en) | 1998-10-21 | 2001-11-27 | Microsoft Corporation | File object synchronization between a desktop computer and a mobile device |
US6363352B1 (en) | 1998-11-13 | 2002-03-26 | Microsoft Corporation | Automatic scheduling and formation of a virtual meeting over a computer network |
US6502113B1 (en) | 1998-11-23 | 2002-12-31 | John E. Crawford | Negotiation manager incorporating clause modification and markers for tracking negotiation progress |
JP2000163344A (en) | 1998-11-27 | 2000-06-16 | Nec Corp | Data base recovery system for network management system |
US7024430B1 (en) | 1998-12-08 | 2006-04-04 | Starfish Software, Inc. | Method and system for implementing a filter in a data synchronization system |
US6681371B1 (en) | 1998-12-21 | 2004-01-20 | At&T Corp. | System and method for using container documents as multi-user domain clients |
KR100309803B1 (en) | 1998-12-26 | 2001-12-17 | 서평원 | Database Synchronization System and Method between Network Management System and Managed Equipment |
US7065633B1 (en) * | 1999-01-28 | 2006-06-20 | Ati International Srl | System for delivering exception raised in first architecture to operating system coded in second architecture in dual architecture CPU |
US6342906B1 (en) | 1999-02-02 | 2002-01-29 | International Business Machines Corporation | Annotation layer for synchronous collaboration |
JP3711210B2 (en) | 1999-03-12 | 2005-11-02 | シャープ株式会社 | Document editing system and program recording medium |
US6687878B1 (en) | 1999-03-15 | 2004-02-03 | Real Time Image Ltd. | Synchronizing/updating local client notes with annotations previously made by other clients in a notes database |
US7007235B1 (en) | 1999-04-02 | 2006-02-28 | Massachusetts Institute Of Technology | Collaborative agent interaction control and synchronization system |
US6317777B1 (en) | 1999-04-26 | 2001-11-13 | Intel Corporation | Method for web based storage and retrieval of documents |
TW428146B (en) | 1999-05-05 | 2001-04-01 | Inventec Corp | Data file updating method by increment |
US6430576B1 (en) | 1999-05-10 | 2002-08-06 | Patrick Gates | Distributing and synchronizing objects |
CN1154054C (en) | 1999-06-04 | 2004-06-16 | 网络装置公司 | Multi-protocol unified file lockout |
US6438548B1 (en) | 1999-06-30 | 2002-08-20 | International Business Machines Corporation | Method of and system for managing documents in a bandwidth constrained environment |
US6678882B1 (en) | 1999-06-30 | 2004-01-13 | Qwest Communications International Inc. | Collaborative model for software systems with synchronization submodel with merge feature, automatic conflict resolution and isolation of potential changes for reuse |
US6327584B1 (en) | 1999-07-30 | 2001-12-04 | Hewlett-Packard Company | Apparatus and method for using version control to dynamically update files while the files are available for access |
US6560620B1 (en) | 1999-08-03 | 2003-05-06 | Aplix Research, Inc. | Hierarchical document comparison system and method |
JP3915331B2 (en) | 1999-08-10 | 2007-05-16 | 富士ゼロックス株式会社 | Shared document editing apparatus and editing method |
US6516339B1 (en) | 1999-08-18 | 2003-02-04 | International Business Machines Corporation | High performance client/server editor |
US6526434B1 (en) | 1999-08-24 | 2003-02-25 | International Business Machines Corporation | System and method for efficient transfer of data blocks from client to server |
US6189009B1 (en) | 1999-08-27 | 2001-02-13 | The Voice.Com, Inc. | System and method for integrating paper-based business documents with computer-readable data entered via a computer network |
US7089278B1 (en) | 1999-09-07 | 2006-08-08 | Fuji Xerox Co., Ltd. | Anchored conversations: adhesive, in-context, virtual discussion forums |
JP2001092707A (en) | 1999-09-24 | 2001-04-06 | Nec Corp | Information processing system, structured document processing system, its updating method and recording medium with its updating program recorded thereon |
US6578054B1 (en) | 1999-10-04 | 2003-06-10 | Microsoft Corporation | Method and system for supporting off-line mode of operation and synchronization using resource state information |
WO2001033362A1 (en) | 1999-11-05 | 2001-05-10 | Attivo Software, Inc. | Action communication and synchronization for documents accessed by multiple users |
US6560614B1 (en) | 1999-11-12 | 2003-05-06 | Xosoft Inc. | Nonintrusive update of files |
US6751618B1 (en) | 1999-11-24 | 2004-06-15 | Unisys Corporation | Method and apparatus for a web application server to upload multiple files and invoke a script to use the files in a single browser request |
AU3435801A (en) | 1999-12-16 | 2001-06-25 | Perimed Compliance Corporation | System and method for electronic archiving and retrieval of medical documents |
US6529905B1 (en) | 2000-01-11 | 2003-03-04 | Frontline Solutions, Inc. | Method and system for allowing multiple users to edit a hierarchical data structure |
JP3879350B2 (en) | 2000-01-25 | 2007-02-14 | 富士ゼロックス株式会社 | Structured document processing system and structured document processing method |
US6694336B1 (en) | 2000-01-25 | 2004-02-17 | Fusionone, Inc. | Data transfer and synchronization system |
SG99886A1 (en) | 2000-02-24 | 2003-11-27 | Ibm | System and method for collaborative multi-device web browsing |
US6842768B1 (en) | 2000-03-01 | 2005-01-11 | Siemens Communications, Inc. | Apparatus and method for selectable compression |
KR100331685B1 (en) | 2000-04-04 | 2002-04-09 | 오길록 | Cooperative appartus for editing documnet and method using the same |
JP2001290690A (en) | 2000-04-11 | 2001-10-19 | Canon Inc | Method and device for managing file and storage medium |
JP3549097B2 (en) | 2000-04-26 | 2004-08-04 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Method for identifying owner of collaborative work object, computer system, and computer-readable recording medium |
ATE297571T1 (en) | 2000-05-16 | 2005-06-15 | Garrett O'carroll | SYSTEM AND METHOD FOR DOCUMENT PROCESSING |
US6931592B1 (en) | 2000-05-22 | 2005-08-16 | Microsoft Corporation | Reviewing and merging electronic documents |
US6757767B1 (en) | 2000-05-31 | 2004-06-29 | Advanced Digital Information Corporation | Method for acceleration of storage devices by returning slightly early write status |
SE522846C2 (en) * | 2000-06-22 | 2004-03-09 | Ericsson Telefon Ab L M | Antenna with helical radiator and feedback conductor, as well as multi-layer cards and portable communication apparatus including such an antenna |
US6596396B2 (en) * | 2000-08-09 | 2003-07-22 | Mitsubishi Gas Chemical Company, Inc. | Thin-film-like particles having skeleton constructed by carbons and isolated films |
US6925476B1 (en) | 2000-08-17 | 2005-08-02 | Fusionone, Inc. | Updating application data including adding first change log to aggreagate change log comprising summary of changes |
US7249314B2 (en) | 2000-08-21 | 2007-07-24 | Thoughtslinger Corporation | Simultaneous multi-user document editing system |
US6681382B1 (en) | 2000-09-18 | 2004-01-20 | Cisco Technology, Inc. | Method and system for using virtual labels in a software configuration management system |
US6976213B1 (en) | 2000-11-10 | 2005-12-13 | Interspec, Inc. | Method of automatically generating specifications and providing online services for same |
US7080076B1 (en) | 2000-11-28 | 2006-07-18 | Attenex Corporation | System and method for efficiently drafting a legal document using an authenticated clause table |
WO2002059773A1 (en) | 2000-12-04 | 2002-08-01 | Thinkshare Corp. | Modular distributed mobile data applications |
US6941326B2 (en) | 2001-01-24 | 2005-09-06 | Microsoft Corporation | Accounting for update notifications in synchronizing data that may be represented by different data structures |
US7110936B2 (en) | 2001-02-23 | 2006-09-19 | Complementsoft Llc | System and method for generating and maintaining software code |
US7058663B2 (en) | 2001-03-13 | 2006-06-06 | Koninklijke Philips Electronics, N.V. | Automatic data update |
EP1381938A4 (en) | 2001-03-16 | 2010-06-09 | Netomat Inc | Sharing, managing and communicating information over a computer network |
JP2002288029A (en) | 2001-03-28 | 2002-10-04 | Ricoh Co Ltd | Document managing system |
US6757678B2 (en) | 2001-04-12 | 2004-06-29 | International Business Machines Corporation | Generalized method and system of merging and pruning of data trees |
US7409424B2 (en) | 2001-04-24 | 2008-08-05 | Parker James A | Electronic mail file access system |
US6993522B2 (en) | 2001-06-27 | 2006-01-31 | Microsoft Corporation | System and method for resolving conflicts detected during a synchronization session |
US7117278B2 (en) | 2001-07-12 | 2006-10-03 | Sun Micro Systems, Inc. | Method for merging a plurality of data streams into a single data stream |
US7124362B2 (en) | 2001-08-31 | 2006-10-17 | Robert Tischer | Method and system for producing an ordered compilation of information with more than one author contributing information contemporaneously |
US7149776B1 (en) | 2001-08-31 | 2006-12-12 | Oracle International Corp. | System and method for real-time co-browsing |
US20040205539A1 (en) | 2001-09-07 | 2004-10-14 | Mak Mingchi Stephen | Method and apparatus for iterative merging of documents |
US20030097410A1 (en) | 2001-10-04 | 2003-05-22 | Atkins R. Travis | Methodology for enabling multi-party collaboration across a data network |
JP2003150586A (en) | 2001-11-12 | 2003-05-23 | Ntt Docomo Inc | Document converting system, document converting method and computer-readable recording medium with document converting program recorded thereon |
JP4215425B2 (en) | 2001-11-21 | 2009-01-28 | 日本電気株式会社 | Text management system, management method thereof, and program thereof |
JP4051924B2 (en) | 2001-12-05 | 2008-02-27 | 株式会社日立製作所 | Network system capable of transmission control |
US6711718B2 (en) | 2001-12-10 | 2004-03-23 | Charles Pfeil | Parallel electronic design automation: distributed simultaneous editing |
US7496841B2 (en) | 2001-12-17 | 2009-02-24 | Workshare Technology, Ltd. | Method and system for document collaboration |
US7475242B2 (en) | 2001-12-18 | 2009-01-06 | Hewlett-Packard Development Company, L.P. | Controlling the distribution of information |
US20030140067A1 (en) | 2002-01-18 | 2003-07-24 | Robert Sesek | Systems and methods for sending documents |
US7024429B2 (en) | 2002-01-31 | 2006-04-04 | Nextpage,Inc. | Data replication based upon a non-destructive data model |
WO2003067448A1 (en) * | 2002-02-02 | 2003-08-14 | E-Wings, Inc. | Distributed system for interactive collaboration |
JP2003233520A (en) | 2002-02-07 | 2003-08-22 | Fujitsu Ltd | File controlling device for file resource on network |
US20030159105A1 (en) | 2002-02-21 | 2003-08-21 | Hiebert Steven P. | Interpretive transformation system and method |
US7340534B2 (en) | 2002-03-05 | 2008-03-04 | Sun Microsystems, Inc. | Synchronization of documents between a server and small devices |
US7200668B2 (en) | 2002-03-05 | 2007-04-03 | Sun Microsystems, Inc. | Document conversion with merging |
US20030208534A1 (en) | 2002-05-02 | 2003-11-06 | Dennis Carmichael | Enhanced productivity electronic meeting system |
WO2003107133A2 (en) | 2002-06-01 | 2003-12-24 | Engedi Technologies, Inc. | Secure remote management appliance |
US7565603B1 (en) | 2002-06-28 | 2009-07-21 | Microsoft Corporation | Representing style information in a markup language document |
JP2004065193A (en) | 2002-08-09 | 2004-03-04 | Kazumi Minbu | Guard for grass cutter |
US6928476B2 (en) | 2002-08-23 | 2005-08-09 | Mirra, Inc. | Peer to peer remote data storage and collaboration |
US7814055B2 (en) | 2002-08-28 | 2010-10-12 | Apple Inc. | Method of managing a calendar and a computer system for implementing that method |
JP4664076B2 (en) | 2002-09-30 | 2011-04-06 | キューナチュラリー システムズ インコーポレイテッド | Blinking annotation callouts to highlight cross-language search results |
JP4737914B2 (en) | 2002-10-02 | 2011-08-03 | ケープレックス・インク | Document revision support program, computer-readable medium storing the support program, and document revision support apparatus |
US20040068505A1 (en) | 2002-10-04 | 2004-04-08 | Chung-I Lee | System and method for synchronously editing a file on different client computers |
CN1244874C (en) | 2002-10-12 | 2006-03-08 | 鸿富锦精密工业(深圳)有限公司 | Multi-point coordinated operation system and method |
DE10250842B4 (en) | 2002-10-31 | 2010-11-11 | OCé PRINTING SYSTEMS GMBH | A method, computer program product and apparatus for processing a document data stream of an input format into an output format |
US7328243B2 (en) * | 2002-10-31 | 2008-02-05 | Sun Microsystems, Inc. | Collaborative content coherence using mobile agents in peer-to-peer networks |
US7818678B2 (en) | 2002-10-31 | 2010-10-19 | Litera Technology Llc | Collaborative document development and review system |
US20040177343A1 (en) | 2002-11-04 | 2004-09-09 | Mcvoy Lawrence W. | Method and apparatus for understanding and resolving conflicts in a merge |
US20040143630A1 (en) | 2002-11-21 | 2004-07-22 | Roy Kaufmann | Method and system for sending questions, answers and files synchronously and asynchronously in a system for enhancing collaboration using computers and networking |
US7954043B2 (en) | 2002-12-02 | 2011-05-31 | International Business Machines Corporation | Concurrent editing of a file by multiple authors |
US7209948B2 (en) | 2002-12-20 | 2007-04-24 | International Business Machines, Corporation | Collaborative review of distributed content |
KR100490734B1 (en) | 2002-12-21 | 2005-05-24 | 한국전자통신연구원 | Annotation-based automatic document generation apparatus and method |
KR100462839B1 (en) | 2002-12-24 | 2004-12-23 | 한국전자통신연구원 | Method for database synchronization and conflict resolution between clients and server of mobile system |
US7337388B2 (en) | 2003-01-02 | 2008-02-26 | Microsoft Corporation | Tool-based iterative document management |
US7389309B2 (en) | 2003-02-28 | 2008-06-17 | Microsoft Corporation | Method for managing file replication in applications |
US8706760B2 (en) | 2003-02-28 | 2014-04-22 | Microsoft Corporation | Method to delay locking of server files on edit |
US8010491B2 (en) | 2003-02-28 | 2011-08-30 | Microsoft Corporation | Method for managing multiple file states for replicated files |
US20060259524A1 (en) | 2003-03-17 | 2006-11-16 | Horton D T | Systems and methods for document project management, conversion, and filing |
US9003295B2 (en) | 2003-03-17 | 2015-04-07 | Leo Martin Baschy | User interface driven access control system and method |
US7757162B2 (en) | 2003-03-31 | 2010-07-13 | Ricoh Co. Ltd. | Document collection manipulation |
US7155465B2 (en) | 2003-04-18 | 2006-12-26 | Lee Howard F | Method and apparatus for automatically archiving a file system |
JP2004326176A (en) | 2003-04-21 | 2004-11-18 | Matsushita Electric Works Ltd | Information server, program for information server and information system |
US20040230896A1 (en) | 2003-05-16 | 2004-11-18 | Dethe Elza | Method and system for enabling collaborative authoring of hierarchical documents with unique node identifications |
US7290251B2 (en) | 2003-05-16 | 2007-10-30 | Microsoft Corporation | Method and system for providing a representation of merge conflicts in a three-way merge operation |
US7660829B2 (en) | 2003-05-30 | 2010-02-09 | Microsoft Corporation | System and method for delegating file system operations |
US7257769B2 (en) | 2003-06-05 | 2007-08-14 | Siemens Communications, Inc. | System and method for indicating an annotation for a document |
US7444337B2 (en) | 2004-03-09 | 2008-10-28 | Ntt Docomo, Inc. | Framework and associated apparatus for the adaptive replication of applications with server side code units |
US7716593B2 (en) | 2003-07-01 | 2010-05-11 | Microsoft Corporation | Conversation grouping of electronic mail records |
SG144930A1 (en) | 2003-07-08 | 2008-08-28 | Us Lynx Llc | An automated publishing system that facilitates collaborative editing and accountability through virtual document architecture |
US7315978B2 (en) | 2003-07-30 | 2008-01-01 | Ameriprise Financial, Inc. | System and method for remote collection of data |
AU2003903994A0 (en) | 2003-07-31 | 2003-08-14 | Canon Kabushiki Kaisha | Collaborative editing with automatic layout |
US20050033811A1 (en) | 2003-08-07 | 2005-02-10 | International Business Machines Corporation | Collaborative email |
US7363581B2 (en) | 2003-08-12 | 2008-04-22 | Accenture Global Services Gmbh | Presentation generator |
US7401104B2 (en) | 2003-08-21 | 2008-07-15 | Microsoft Corporation | Systems and methods for synchronizing computer systems through an intermediary file system share or device |
US7302274B2 (en) | 2003-09-19 | 2007-11-27 | Nokia Corporation | Method and device for real-time shared editing mobile video |
US7143117B2 (en) | 2003-09-25 | 2006-11-28 | International Business Machines Corporation | Method, system, and program for data synchronization by determining whether a first identifier for a portion of data at a first source and a second identifier for a portion of corresponding data at a second source match |
US7242389B1 (en) | 2003-10-07 | 2007-07-10 | Microsoft Corporation | System and method for a large format collaborative display for sharing information |
US7831679B2 (en) * | 2003-10-15 | 2010-11-09 | Microsoft Corporation | Guiding sensing and preferences for context-sensitive services |
US7185277B1 (en) | 2003-10-24 | 2007-02-27 | Microsoft Corporation | Method and apparatus for merging electronic documents containing markup language |
WO2005043279A2 (en) | 2003-10-31 | 2005-05-12 | Disksites Research And Development Ltd. | Device, system and method for storage and access of computer files |
US20050097440A1 (en) | 2003-11-04 | 2005-05-05 | Richard Lusk | Method and system for collaboration |
US7203708B2 (en) | 2003-11-06 | 2007-04-10 | Microsoft Corporation | Optimizing file replication using binary comparisons |
US7839532B2 (en) | 2003-12-12 | 2010-11-23 | Ipro Tech, Inc. | Methods and apparatus for imaging documents |
US20050177617A1 (en) | 2003-12-23 | 2005-08-11 | Intel Corporation | Conflict resolution during data synchronization |
US7225189B1 (en) | 2004-02-19 | 2007-05-29 | Microsoft Corporation | Data source write back and offline data editing and storage in a spreadsheet |
JP2005267021A (en) | 2004-03-17 | 2005-09-29 | Ricoh Co Ltd | Document preparation method and device, program, storage medium and data structure of document |
US20050216524A1 (en) | 2004-03-23 | 2005-09-29 | Integrated Data Corporation | Smart and selective synchronization between databases in a document management system |
US7912904B2 (en) | 2004-03-31 | 2011-03-22 | Google Inc. | Email system with conversation-centric user interface |
JP2005301838A (en) | 2004-04-14 | 2005-10-27 | Sharp Corp | Information processor, information processing system, file simultaneous editing method and file simultaneous editing program |
US7818679B2 (en) | 2004-04-20 | 2010-10-19 | Microsoft Corporation | Method, system, and apparatus for enabling near real time collaboration on an electronic document through a plurality of computer systems |
JP2005309745A (en) | 2004-04-21 | 2005-11-04 | Nec Corp | Document management network system for managing original image document information and postscript information, and image document delivery server |
JP4448537B2 (en) | 2004-04-26 | 2010-04-14 | コダック グラフィック コミュニケーションズ カナダ カンパニー | System and method for comparing documents containing graphic elements |
US7536636B2 (en) | 2004-04-26 | 2009-05-19 | Kodak Graphic Communications Canada Company | Systems and methods for comparing documents containing graphic elements |
WO2005114467A2 (en) | 2004-05-19 | 2005-12-01 | Universität Zürich | Computer-based system and computer program product for collaborative editing of documents |
US20060030292A1 (en) | 2004-05-20 | 2006-02-09 | Bea Systems, Inc. | Client programming for mobile client |
US7603357B1 (en) | 2004-06-01 | 2009-10-13 | Adobe Systems Incorporated | Collaborative asset management |
JP4716709B2 (en) | 2004-06-10 | 2011-07-06 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Structured document processing apparatus, structured document processing method, and program |
JP4069905B2 (en) | 2004-06-28 | 2008-04-02 | コニカミノルタビジネステクノロジーズ株式会社 | Shared file management system and server |
JP2006031292A (en) | 2004-07-14 | 2006-02-02 | Fuji Xerox Co Ltd | Document processing apparatus, document processing method, and document processing program |
US7567988B2 (en) | 2004-07-16 | 2009-07-28 | Sap Ag | Synchronizing agent for multiple clients/applications on a computer system |
US7487471B2 (en) | 2004-07-23 | 2009-02-03 | Sap Ag | User interface for conflict resolution management |
US7966556B1 (en) | 2004-08-06 | 2011-06-21 | Adobe Systems Incorporated | Reviewing and editing word processing documents |
US20060041596A1 (en) | 2004-08-19 | 2006-02-23 | Vlad Stirbu | Caching directory server data for controlling the disposition of multimedia data on a network |
JP2008511881A (en) | 2004-08-31 | 2008-04-17 | ▲騰▼▲訊▼科技(深▲セン▼)有限公司 | Communication system and method for implementing online file storage based on instant messaging platform |
US20060047656A1 (en) | 2004-09-01 | 2006-03-02 | Dehlinger Peter J | Code, system, and method for retrieving text material from a library of documents |
US20060053195A1 (en) | 2004-09-03 | 2006-03-09 | Schneider Ronald E | Systems and methods for collaboration |
US20060053194A1 (en) | 2004-09-03 | 2006-03-09 | Schneider Ronald E | Systems and methods for collaboration |
US20060080432A1 (en) | 2004-09-03 | 2006-04-13 | Spataro Jared M | Systems and methods for collaboration |
US20070118794A1 (en) | 2004-09-08 | 2007-05-24 | Josef Hollander | Shared annotation system and method |
US7392243B2 (en) | 2004-10-20 | 2008-06-24 | Microsoft Corporation | Using permanent identifiers in documents for change management |
US7814105B2 (en) | 2004-10-27 | 2010-10-12 | Harris Corporation | Method for domain identification of documents in a document database |
US7577906B2 (en) | 2004-11-08 | 2009-08-18 | Microsoft Corporation | Method and system for document assembly |
US7472341B2 (en) | 2004-11-08 | 2008-12-30 | International Business Machines Corporation | Multi-user, multi-timed collaborative annotation |
US20060106879A1 (en) | 2004-11-16 | 2006-05-18 | International Business Machines Corporation | Conflict resolution in a synchronization framework |
US7650336B1 (en) * | 2004-12-02 | 2010-01-19 | Adobe Systems Incorporated | File system atomic lock |
US8108773B2 (en) | 2004-12-17 | 2012-01-31 | Xerox Corporation | Method and apparatus for generating instances of documents |
US7617229B2 (en) | 2004-12-20 | 2009-11-10 | Microsoft Corporation | Management and use of data in a computer-generated document |
US7908247B2 (en) | 2004-12-21 | 2011-03-15 | Nextpage, Inc. | Storage-and transport-independent collaborative document-management system |
US7593943B2 (en) | 2005-01-14 | 2009-09-22 | Microsoft Corporation | Method and system for synchronizing multiple user revisions to a shared object |
US20060173901A1 (en) | 2005-01-31 | 2006-08-03 | Mediatek Incorporation | Methods for merging files and related systems |
US20060179026A1 (en) | 2005-02-04 | 2006-08-10 | Bechtel Michael E | Knowledge discovery tool extraction and integration |
US7313580B2 (en) | 2005-02-08 | 2007-12-25 | Domenico Vellante | Systems and methods for sharing information between a user group and associated document |
US7720890B2 (en) | 2005-02-22 | 2010-05-18 | Microsoft Corporation | Ghosted synchronization |
US7792788B2 (en) | 2005-03-04 | 2010-09-07 | Microsoft Corporation | Method and system for resolving conflicts operations in a collaborative editing environment |
US20060218476A1 (en) | 2005-03-25 | 2006-09-28 | Xerox Corporation | Collaborative document authoring and production methods and systems |
US20070016650A1 (en) | 2005-04-01 | 2007-01-18 | Gilbert Gary J | System and methods for collaborative development of content over an electronic network |
RU50695U1 (en) | 2005-04-28 | 2006-01-20 | ФЕДЕРАЛЬНОЕ ГОСУДАРСТВЕННОЕ УНИТАРНОЕ ПРЕДПРИЯТИЕ "ГЛАВНОЕ ПРОИЗВОДСТВЕННО-КОММЕРЧЕСКОЕ УПРАВЛЕНИЕ ПО ОБСЛУЖИВАНИЮ ДИПЛОМАТИЧЕСКОГО КОРПУСА ПРИ МИНИСТЕРСТВЕ ИНОСТРАННЫХ ДЕЛ РОССИЙСКОЙ ФЕДЕРАЦИИ" (ГлавУпДК при МИД России) | DATA STORAGE AND PROCESSING SYSTEM |
US7454406B2 (en) | 2005-04-29 | 2008-11-18 | Adaptec, Inc. | System and method of handling file metadata |
US7536641B2 (en) | 2005-04-29 | 2009-05-19 | Google Inc. | Web page authoring tool for structured documents |
US20060265377A1 (en) | 2005-05-19 | 2006-11-23 | Trimergent | Personalizable information networks |
RU2304803C2 (en) | 2005-06-27 | 2007-08-20 | Евгений Михайлович Растворов | System for registration of operations with data stored on information storage devices |
US7610287B1 (en) | 2005-06-28 | 2009-10-27 | Google Inc. | System and method for impromptu shared communication spaces |
US7779347B2 (en) | 2005-09-02 | 2010-08-17 | Fourteen40, Inc. | Systems and methods for collaboratively annotating electronic documents |
TWI276325B (en) | 2005-09-16 | 2007-03-11 | Hon Hai Prec Ind Co Ltd | Mobile communication device and method for downloading configuration files thereof and wireless communication system |
CN101268458A (en) | 2005-09-22 | 2008-09-17 | 佳思腾软件公司 | Data managing apparatus, data editing apparatus, data browsing apparatus, data managing method, data editing method, and data browsing method |
JP2007115131A (en) | 2005-10-21 | 2007-05-10 | Canon Inc | Information processor and its control method, information processing system, computer program, and storage medium |
GB0523703D0 (en) | 2005-11-22 | 2005-12-28 | Ibm | Collaborative editing of a document |
US8015194B2 (en) | 2005-12-29 | 2011-09-06 | Ricoh Co., Ltd. | Refining based on log content |
US7529780B1 (en) | 2005-12-30 | 2009-05-05 | Google Inc. | Conflict management during data object synchronization between client and server |
US7774703B2 (en) | 2006-02-09 | 2010-08-10 | Microsoft Corporation | Virtual shadow awareness for multi-user editors |
US20070198952A1 (en) | 2006-02-21 | 2007-08-23 | Pittenger Robert A | Methods and systems for authoring of a compound document following a hierarchical structure |
US20070226604A1 (en) | 2006-03-22 | 2007-09-27 | Chalasani Nanchariah R | System and method for merging a sub-document into a collaboratively authored master document |
US8566301B2 (en) | 2006-05-01 | 2013-10-22 | Steven L. Rueben | Document revisions in a collaborative computing environment |
GB0610116D0 (en) | 2006-05-20 | 2006-06-28 | Ibm | A method, apparatus and computer program for collaborative editing of a document |
US8407670B2 (en) | 2006-06-02 | 2013-03-26 | Microsoft Corporation | Collaborative code conflict detection, notification and resolution |
US20080059539A1 (en) | 2006-08-08 | 2008-03-06 | Richard Chin | Document Collaboration System and Method |
US7801951B2 (en) | 2006-08-25 | 2010-09-21 | Reframe-It, Inc. | Process for referencing, prioritizing, accessing, and displaying marginalia in digital media |
US8401841B2 (en) | 2006-08-31 | 2013-03-19 | Orcatec Llc | Retrieval of documents using language models |
WO2008031625A2 (en) | 2006-09-15 | 2008-03-20 | Exbiblio B.V. | Capture and display of annotations in paper and electronic documents |
US9207933B2 (en) | 2006-10-10 | 2015-12-08 | International Business Machines Corporation | Identifying authors of changes between multiple versions of a file |
JP5437557B2 (en) | 2006-10-19 | 2014-03-12 | 富士通株式会社 | Search processing method and search system |
US20080098294A1 (en) | 2006-10-23 | 2008-04-24 | Mediq Learning, L.L.C. | Collaborative annotation of electronic content |
US20080114740A1 (en) | 2006-11-14 | 2008-05-15 | Xcential Group Llc | System and method for maintaining conformance of electronic document structure with multiple, variant document structure models |
US8769006B2 (en) | 2006-11-28 | 2014-07-01 | International Business Machines Corporation | Role-based display of document renditions for web conferencing |
US20080177782A1 (en) | 2007-01-10 | 2008-07-24 | Pado Metaware Ab | Method and system for facilitating the production of documents |
RU2327206C1 (en) | 2007-01-17 | 2008-06-20 | Федеральное государственное унитарное предприятие "Научно-исследовательский институт "Восход" | System for isolated access to documents in distributed network for electronic document management |
JP2008186176A (en) | 2007-01-29 | 2008-08-14 | Canon Inc | Image processing apparatus, document merging method and control program |
KR100904758B1 (en) | 2007-02-08 | 2009-06-29 | 삼성전자주식회사 | Flash memory device and system including buffer memory, and data updating method of the flash memory device |
EP2122510A2 (en) | 2007-02-14 | 2009-11-25 | Museami, Inc. | Music-based search engine |
US20080294895A1 (en) | 2007-02-15 | 2008-11-27 | Michael Bodner | Disaggregation/reassembly method system for information rights management of secure documents |
US8868504B2 (en) * | 2007-03-07 | 2014-10-21 | Oracle International Corporation | Database system with active standby and nodes |
US7949938B2 (en) | 2007-03-20 | 2011-05-24 | International Business Machines Corporation | Comparing and merging multiple documents |
US8019780B1 (en) | 2007-03-30 | 2011-09-13 | Google Inc. | Handling document revision history information in the presence of a multi-user permissions model |
US20080256114A1 (en) | 2007-04-10 | 2008-10-16 | Microsoft Corporation | Techniques to display associated information between application programs |
US8024652B2 (en) | 2007-04-10 | 2011-09-20 | Microsoft Corporation | Techniques to associate information between application programs |
US8504553B2 (en) | 2007-04-19 | 2013-08-06 | Barnesandnoble.Com Llc | Unstructured and semistructured document processing and searching |
JP5154832B2 (en) | 2007-04-27 | 2013-02-27 | 株式会社日立製作所 | Document search system and document search method |
US8082277B1 (en) | 2007-06-05 | 2011-12-20 | The Board of Trustees of the University of Alabama, for and on behalf of the University of Alabamaiin Huntsville | Systems and methods for generating technical documents |
US20080320384A1 (en) | 2007-06-25 | 2008-12-25 | Ramesh Nagarajan | Automated addition of images to text |
US8239760B2 (en) | 2007-06-26 | 2012-08-07 | Sap Ag | Multi-user document editing system and method |
US7937663B2 (en) | 2007-06-29 | 2011-05-03 | Microsoft Corporation | Integrated collaborative user interface for a document editor program |
US7933952B2 (en) | 2007-06-29 | 2011-04-26 | Microsoft Corporation | Collaborative document authoring |
JP5334335B2 (en) | 2007-07-02 | 2013-11-06 | フラウンホファー・ゲゼルシャフト・ツール・フォルデルング・デル・アンゲバンテン・フォルシュング・アインゲトラーゲネル・フェライン | Apparatus and method for storing and retrieving files having media data containers and metadata containers |
WO2009027138A1 (en) * | 2007-08-30 | 2009-03-05 | International Business Machines Corporation | Accessing data entities |
US8595202B2 (en) | 2007-10-03 | 2013-11-26 | Siemens Aktiengesellschaft | Method and system for intra-document object locking in collaborative authoring |
US8280892B2 (en) | 2007-10-05 | 2012-10-02 | Fujitsu Limited | Selecting tags for a document by analyzing paragraphs of the document |
US8028229B2 (en) | 2007-12-06 | 2011-09-27 | Microsoft Corporation | Document merge |
US7797274B2 (en) | 2007-12-12 | 2010-09-14 | Google Inc. | Online content collaboration model |
US8291308B2 (en) | 2007-12-28 | 2012-10-16 | International Business Machines Corporation | Annotating collaborative information structures |
US8301588B2 (en) | 2008-03-07 | 2012-10-30 | Microsoft Corporation | Data storage for file updates |
US20090249224A1 (en) | 2008-03-31 | 2009-10-01 | Microsoft Corporation | Simultaneous collaborative review of a document |
US8352870B2 (en) | 2008-04-28 | 2013-01-08 | Microsoft Corporation | Conflict resolution |
US8825594B2 (en) | 2008-05-08 | 2014-09-02 | Microsoft Corporation | Caching infrastructure |
US8429753B2 (en) | 2008-05-08 | 2013-04-23 | Microsoft Corporation | Controlling access to documents using file locks |
US8417666B2 (en) | 2008-06-25 | 2013-04-09 | Microsoft Corporation | Structured coauthoring |
US8332359B2 (en) | 2008-07-28 | 2012-12-11 | International Business Machines Corporation | Extended system for accessing electronic documents with revision history in non-compatible repositories |
US10747952B2 (en) | 2008-09-15 | 2020-08-18 | Palantir Technologies, Inc. | Automatic creation and server push of multiple distinct drafts |
US8286132B2 (en) | 2008-09-25 | 2012-10-09 | International Business Machines Corporation | Comparing and merging structured documents syntactically and semantically |
US20100095198A1 (en) | 2008-10-15 | 2010-04-15 | Apple Inc. | Shared comments for online document collaboration |
US20100131836A1 (en) | 2008-11-24 | 2010-05-27 | Microsoft Corporation | User-authored notes on shared documents |
US8346768B2 (en) | 2009-04-30 | 2013-01-01 | Microsoft Corporation | Fast merge support for legacy documents |
-
2008
- 2008-05-08 US US12/117,025 patent/US8825594B2/en active Active
-
2012
- 2012-06-13 US US13/495,659 patent/US20120254315A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090125518A1 (en) * | 2007-11-09 | 2009-05-14 | Microsoft Corporation | Collaborative Authoring |
US20090157811A1 (en) * | 2007-12-14 | 2009-06-18 | Microsoft Corporation | Collaborative Authoring Modes |
Non-Patent Citations (1)
Title |
---|
Preston, Jon A. et al, "An Efficient Synchronous Collaborative Editing System Employing Dynamic Locking of Varying Granularity in Generalized Document Trees", November 17-20, 2006, pp. 1-10. * |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8990150B2 (en) | 2007-11-09 | 2015-03-24 | Microsoft Technology Licensing, Llc | Collaborative authoring |
US10394941B2 (en) | 2007-11-09 | 2019-08-27 | Microsoft Technology Licensing, Llc | Collaborative authoring |
US8352418B2 (en) | 2007-11-09 | 2013-01-08 | Microsoft Corporation | Client side locking |
US9547635B2 (en) | 2007-11-09 | 2017-01-17 | Microsoft Technology Licensing, Llc | Collaborative authoring |
US8825758B2 (en) | 2007-12-14 | 2014-09-02 | Microsoft Corporation | Collaborative authoring modes |
US20140373108A1 (en) | 2007-12-14 | 2014-12-18 | Microsoft Corporation | Collaborative authoring modes |
US10057226B2 (en) | 2007-12-14 | 2018-08-21 | Microsoft Technology Licensing, Llc | Collaborative authoring modes |
US20090271696A1 (en) * | 2008-04-28 | 2009-10-29 | Microsoft Corporation | Conflict Resolution |
US8352870B2 (en) | 2008-04-28 | 2013-01-08 | Microsoft Corporation | Conflict resolution |
US9760862B2 (en) | 2008-04-28 | 2017-09-12 | Microsoft Technology Licensing, Llc | Conflict resolution |
US8429753B2 (en) | 2008-05-08 | 2013-04-23 | Microsoft Corporation | Controlling access to documents using file locks |
US8825594B2 (en) | 2008-05-08 | 2014-09-02 | Microsoft Corporation | Caching infrastructure |
US8417666B2 (en) | 2008-06-25 | 2013-04-09 | Microsoft Corporation | Structured coauthoring |
US8346768B2 (en) | 2009-04-30 | 2013-01-01 | Microsoft Corporation | Fast merge support for legacy documents |
Also Published As
Publication number | Publication date |
---|---|
US8825594B2 (en) | 2014-09-02 |
US20090282041A1 (en) | 2009-11-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8825594B2 (en) | Caching infrastructure | |
US10057226B2 (en) | Collaborative authoring modes | |
US10606809B2 (en) | Multi-master text synchronization using deltas | |
US10755234B2 (en) | System and method for offline synchronization of exception items of shared services for client applications | |
CN106663089B (en) | Intelligent conflict detection and semantic expression for document editing | |
CN109313634B (en) | File synchronization pause for single file | |
US7941399B2 (en) | Collaborative authoring | |
US8984392B2 (en) | Document synchronization over stateless protocols | |
US8219920B2 (en) | Methods and systems for managing to do items or notes or electronic messages | |
US9026935B1 (en) | Application user interface with an interactive overlay | |
US20130191451A1 (en) | Presence-based Synchronization | |
US20090327358A1 (en) | Resolving conflicts in content management systems | |
KR101919180B1 (en) | Synchronizing conversation structures in web-based email systems | |
US7818293B2 (en) | Method and system to synchronize updated versions of a document edited on a collaborative site that are under document management control | |
KR20110129898A (en) | Integration of pre-meeting and post-meeting experience into a meeting lifecycle | |
US20120102232A1 (en) | Bidirectional synchronization with crm applications | |
US20100262647A1 (en) | Granular data synchronization for editing multiple data objects | |
US10866926B2 (en) | Hybrid search interface |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034544/0541 Effective date: 20141014 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |