| Patent application number | Description | Published |
|---|
| 20090282041 | Caching Infrastructure - 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. | 11-12-2009 |
| 20090282462 | Controlling Access to Documents Using File Locks - Examples are related to systems and methods for controlling access to document files on a document server. One example system includes document files stored on a document server, at least one of the document files referencing a file lock, and a document access processing module. The example document access processing module includes a file sharing processing module that determines a coauthoring status of a software application of a client computer requesting access to the document file, and a file lock processing module that stores one or more file locks and that controls the setting and resetting of file locks. The example document access processing module uses the coauthoring status of the software application and the file lock status of a document file to determine whether a software application is permitted to have write access to the document file. | 11-12-2009 |
| 20100211543 | SYNCHRONIZING METADATA AND DOCUMENT CONTENT ACROSS CLIENT SYSTEMS USING DIFFERENT COMMUNICATION CHANNELS - Tools and techniques for synchronizing metadata and document content across client systems using different communication channels are provided. These tools may define logical communication channels between client software components, and may allocate one of these channels to synchronizing updates to the contents of documents shared between these client components. These tools may allocate another one of the communication channels to synchronizing metadata between the client components, with the metadata describing activity pertaining to the shared documents. The client components may receive indications of activity made by users to the document contents, and may create metadata representing the activity. These client components may then transmit this metadata, using the further communication channel, to any number of other client components automatically in real time with the updates. | 08-19-2010 |
| 20100281007 | Cross-Channel Coauthoring Consistency - A computing device includes a processing unit, and a memory with instructions that, when executed by the processing unit, cause the processing unit to create: a document processing module that processes the creation and editing of document content; and a metadata processing module that generates, monitors and stores metadata for a document on the computing device, the metadata processing module generating lock creation metadata that include information about a new lock that is created when a user begins to edit a portion of a document, lock removal metadata that includes information about removing a lock, and lock deletion metadata that includes information about deleting a lock, the metadata processing module writing lock creation metadata to both a data channel and to a separate metadata channel, the metadata processing module writing lock removal metadata to the data channel and the metadata processing module writing lock deletion metadata to the metadata channel. | 11-04-2010 |
| 20110208854 | DYNAMIC TRAFFIC CONTROL USING FEEDBACK LOOP - A feedback loop is created between a server and clients that provides the clients with health information of the server to assist in client-server traffic control. Health information is calculated for the server that measures a current health of the server. The health information is automatically provided to a client by the server in response to a request made by the client. The clients can utilize the received health information to determine when to request resources from the server. | 08-25-2011 |
| 20110302237 | Client-Server Interaction Frequency Control - Client-server interaction frequency control may be provided. First, a collaborative electronic document may be loaded at a client device in a document collaboration session. The client device may then request a client-server interaction with a server hosting the collaboration session. Next, the client may receive input from the server indicating a state of the server. This input may then be used by the client device to adjust a rate at which the requested client-server interaction may occur. | 12-08-2011 |
| Patent application number | Description | Published |
|---|
| 20090125518 | Collaborative Authoring - A collaborative authoring application provides an authoring environment in which two or more users can edit a document concurrently. Each user edits a copy of the document, sends updates to a master copy of the document, and receives updates from the master copy of the document. The authoring environment generally inhibits the users from providing conflicting editing instructions to the master copy of the document. For example, each user can generate a content lock about one or more data units within the document. The authoring environment may synchronize content locks automatically and content only at the request of the user. | 05-14-2009 |
| 20090150394 | Document Merge - Methods and systems of merging a first document with at least a second document to generate a third document. Each of the first and second documents includes at least one data unit. Each data unit is associated with a unit identifier and an edit identifier. The unit identifiers of each of the documents are compared to the unit identifiers of the other document to determine whether each unit identifier is a matching or non-matching unit identifier. Edit identifiers of the data units associated with the matching unit identifiers are compared to each other. Data units associated with the non-matching unit identifiers are inserted directly into the third document. Data units associated with the matching unit identifiers and the matching edit identifiers are inserted directly into the third document. Data units associated with the matching unit identifiers and the non-matching edit identifiers are merged into the third document. | 06-11-2009 |
| 20090157811 | Collaborative Authoring Modes - A collaborative authoring application provides an authoring environment in which two or more users can edit a document concurrently. Each user edits a copy of the document, sends updates to a master copy of the document, and receives updates from the master copy of the document. The authoring environment may be configured into a public mode of operation, in which content and metadata are synchronized automatically, or into a private mode of operation, in which metadata is synchronized automatically and content is synchronized only at the request of the user. The authoring application may edit documents offline in public or private mode. | 06-18-2009 |
| 20110184906 | Client Side Locking - A collaborative authoring application provides an authoring environment in which two or more users can edit a document concurrently. Each user edits a copy of the document, sends updates to a master copy of the document, and receives updates from the master copy of the document. The authoring environment generally inhibits the users from providing conflicting editing instructions to the master copy of the document. For example, each user can generate a content lock about one or more data units within the document. The authoring environment may synchronize content locks automatically and content only at the request of the user. | 07-28-2011 |
| Patent application number | Description | Published |
|---|
| 20080229199 | Customizing help content - A method for providing customized help, the method comprising: retrieving a first help content from a first help datastore in response to a help request received from a user, the first help datastore storing a plurality of help content each associated with a respective help identifier; retrieving a second help content from a second help datastore, the second help datastore storing a plurality of help content each associated with a respective help identifier, the second help content having the same help identifier as the first help content; generating a help presentation file comprising the first help content and the second help content; wherein one the first help datastore or the second help datastore is editable by the user and the other help datastore is non-editable by the user. | 09-18-2008 |
| 20080256495 | Personalized user interface - A user interface of a computing system is personalized based on whether the computing system is used in a home environment, a business environment, etc. In one implementation, user interface content is stored that is defined for a plurality of consumer-usage environments, such as the home and business environment. The computing system identifies its consumer-usage environment, whether it is a home environment, a business environment, etc. The computing system then personalizes a user interface that is provided to a user based the environment in which it is being or will be used. To personalize the user interface, the computing system identifies the proper user interface content defined for the consumer-usage environment, and provides the user interface based on the proper user interface content. | 10-16-2008 |
