Abstract: Optimistic concurrency is effectuated to manage constraints in a synchronization environment at multiple computing device endpoints in a consistent fashion without utilizing concentrated centralized constraint logic. Implemented data synchronization constraints that identify false violation scenarios may be automatically resolved without user intervention by using an etag system directed by a master component to assist computing device endpoints to maintain data synchronization among them. Data entries defining each file hierarchy component to be synched are generated and shared with the master component and each computing device endpoint in a synchronization environment. Individual computing device endpoints can use the data entries generated locally with those generated by other computing device endpoints to locally resolve identified false violation scenarios.

Abstract: Optimistic concurrency is effectuated to manage constraints in a synchronization environment at multiple computing device endpoints in a consistent fashion without utilizing concentrated centralized constraint logic. Implemented data synchronization constraints that identify false violation scenarios may be automatically resolved without user intervention by using an etag system directed by a master component to assist computing device endpoints to maintain data synchronization among them. Data entries defining each file hierarchy component to be synched are generated and shared with the master component and each computing device endpoint in a synchronization environment. Individual computing device endpoints can use the data entries generated locally with those generated by other computing device endpoints to locally resolve identified false violation scenarios.

Abstract: A method for synchronizing files is provided. Current metadata including a filename and a hash identifier for each file of the synchronized folder is created. The current metadata is compared to previous metadata. Based on the comparison, a first file and a first folder added to the synchronized folder and a second file and a second folder deleted from the synchronized folder are identified. The hash identifiers of the first and second files are compared. If the hash identifiers match, the filenames of the first and second files are compared. If the filenames do not match, the first file is identified as a renamed file. Metadata is sent to a synchronized device with information related to the first folder sent before information related to the first file, which is sent before information related to the second folder.

Abstract: A method for synchronizing files is provided. Current metadata including a filename and a hash identifier for each file of the synchronized folder is created. The current metadata is compared to previous metadata. Based on the comparison, a first file and a first folder added to the synchronized folder and a second file and a second folder deleted from the synchronized folder are identified. The hash identifiers of the first and second files are compared. If the hash identifiers match, the filenames of the first and second files are compared. If the filenames do not match, the first file is identified as a renamed file. Metadata is sent to a synchronized device with information related to the first folder sent before information related to the first file, which is sent before information related to the second folder.

Abstract: Optimistic concurrency is effectuated to manage constraints in a synchronization environment at multiple computing device endpoints in a consistent fashion without utilizing concentrated centralized constraint logic. Implemented data synchronization constraints that identify false violation scenarios may be automatically resolved without user intervention by using an stag system directed by a master component to assist computing device endpoints to maintain data synchronization among them. Data entries defining each file hierarchy component to be synched are generated and shared with the master component and each computing device endpoint in a synchronization environment. Individual computing device endpoints can use the data entries generated locally with those generated by other computing device endpoints to locally resolve identified false violation scenarios.

Abstract: Optimistic concurrency is effectuated to manage constraints in a synchronization environment at multiple computing device endpoints in a consistent fashion without utilizing concentrated centralized constraint logic. Implemented data synchronization constraints that identify false violation scenarios may be automatically resolved without user intervention by using an etag system directed by a master component to assist computing device endpoints to maintain data synchronization among them. Data entries defining each file hierarchy component to be synched are generated and shared with the master component and each computing device endpoint in a synchronization environment. Individual computing device endpoints can use the data entries generated locally with those generated by other computing device endpoints to locally resolve identified false violation scenarios.

Abstract: Optimistic concurrency is effectuated to manage constraints in a synchronization environment at multiple computing device endpoints in a consistent fashion without utilizing concentrated centralized constraint logic. Implemented data synchronization constraints that identify false violation scenarios may be automatically resolved without user intervention by using an etag system directed by a master component to assist computing device endpoints to maintain data synchronization among them. Data entries defining each file hierarchy component to be synched are generated and shared with the master component and each computing device endpoint in a synchronization environment. Individual computing device endpoints can use the data entries generated locally with those generated by other computing device endpoints to locally resolve identified false violation scenarios.

Abstract: A file fetcher manager provides commonly-utilized management and resource allocation for multiple file fetchers that each implement a different type of mechanism or protocol for transferring data files between peer endpoints in meshes associated with a cloud-computing service. Each file fetcher is configured with both client-side and server-side components to retrieve and serve out data files. The file fetcher manager encapsulates the file fetchers to provide an abstract interface to callers while hiding the underlying details of the file fetchers. The file fetcher manager is arranged for managing simultaneous operations of the multiple file fetchers to route requests from the callers to the appropriate file fetchers, and for scheduling work items for the file fetchers so that data transfers efficiently utilize available resources while keeping the entire transfer process coherent and organized.

Abstract: A method for synchronizing files is provided. Current metadata including a filename and a hash identifier for each file of the synchronized folder is created. The current metadata is compared to previous metadata. Based on the comparison, a first file and a first folder added to the synchronized folder and a second file and a second folder deleted from the synchronized folder are identified. The hash identifiers of the first and second files are compared. If the hash identifiers match, the filenames of the first and second files are compared. If the filenames do not match, the first file is identified as a renamed file. Metadata is sent to a synchronized device with information related to the first folder sent before information related to the first file, which is sent before information related to the second folder.

Abstract: A method for synchronizing files is provided. Current metadata including a filename and a hash identifier for each file of the synchronized folder is created. The current metadata is compared to previous metadata. Based on the comparison, a first file and a first folder added to the synchronized folder and a second file and a second folder deleted from the synchronized folder are identified. The hash identifiers of the first and second files are compared. If the hash identifiers match, the filenames of the first and second files are compared. If the filenames do not match, the first file is identified as a renamed file. Metadata is sent to a synchronized device with information related to the first folder sent before information related to the first file, which is sent before information related to the second folder.

Abstract: Optimistic concurrency is effectuated to manage constraints in a synchronization environment at multiple computing device endpoints in a consistent fashion without utilizing concentrated centralized constraint logic. Implemented data synchronization constraints that identify false violation scenarios may be automatically resolved without user intervention by using an etag system directed by a master component to assist computing device endpoints to maintain data synchronization among them. Data entries defining each file hierarchy component to be synched are generated and shared with the master component and each computing device endpoint in a synchronization environment. Individual computing device endpoints can use the data entries generated locally with those generated by other computing device endpoints to locally resolve identified false violation scenarios.

Abstract: Synchronization of data across multiple endpoints in a mesh network that supports a data sharing service is throttled responsively to user activity in the network by monitoring the activity using a component in a mesh operating environment (“MOE”) runtime that is instantiated on each endpoint. The monitoring may include the collection of data that can be used to infer user activity, as well as data that explicitly indicates activity. State information is maintained so that data can be synchronized across the endpoints even when a user goes offline from the service. When the user logs on to the service, makes changes to a shared file, or the endpoint device starts up upon connection to a mesh network, throttling is performed by prioritizing work items associated with synchronization operations so that resources on the endpoint are not excessively consumed which could reduce the quality of the user experience.

Abstract: A file fetcher manager provides commonly-utilized management and resource allocation for multiple file fetchers that each implement a different type of mechanism or protocol for transferring data files between peer endpoints in meshes associated with a cloud-computing service. Each file fetcher is configured with both client-side and server-side components to retrieve and serve out data files. The file fetcher manager encapsulates the file fetchers to provide an abstract interface to callers while hiding the underlying details of the file fetchers. The file fetcher manager is arranged for managing simultaneous operations of the multiple file fetchers to route requests from the callers to the appropriate file fetchers, and for scheduling work items for the file fetchers so that data transfers efficiently utilize available resources while keeping the entire transfer process coherent and organized.

Abstract: The present invention relates to herpes viral mutants and methods of using these viral mutants for selectively targeting tumor cells or other populations of target cells. The viral mutants of the invention are capable of selective targeting due to the use of tumor-specific and/or cell-specific promoters to drive expression of the herpes ?34.5 gene.

Abstract: The present invention relates to herpes viral mutants and methods of using these viral mutants for selectively targeting tumor cells or other populations of target cells. The viral mutants of the invention are capable of selective targeting due to the use of tumor-specific and/or cell-specific promoters to drive expression of the herpes ?34.5 gene.

Abstract: A system for facilitating collaboration among a plurality of users in connection with generation of a document includes a document information store and one or more user modules. The document information store stores document information relating to documents being generated, the document information including both document structure information and document content information, the document structure information describing document structural elements for each one document and document content information comprising document content elements associated with respective document structural elements. Each user module includes a whiteboard display module, a document update module and an interface module. The whiteboard display module is configured to display a whiteboard to a user, the whiteboard selectively displaying document structure defined by the document structural elements for a document and document content information therefor.