Abstract: Content maintained in a first repository of a first installation (which can optionally be an on-premise installation) of a content management system, as well as metadata associated with the content, can be shared via an approach in which content items maintained in the first repository are synchronized with a copy of the content items maintained in a second repository of a second installation (which can optionally be a cloud-based installation). The first installation can be optionally firewall protected. The copy of the content items can be accessed by collaborative users both within and external to a firewall. Related systems, methods, products, etc. are described.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: A synchronization queuing service associated with a content management system repository can record file events occurring to content items maintained at the content management system repository. The synchronization queuing service can receive a file synchronization request for information identifying a content item to which a client machine is subscribed. The synchronization queuing service can determine consistency or inconsistency of a client machine state of the content item relative to the content item at the content management system repository and can respond to client machine with a file event summary comprising information usable by the client machine to identify actions necessary to synchronize the client machine state of the content item the content item.

Abstract: Content maintained in a first repository of a first installation (which can optionally be an on-premise installation) of a content management system, as well as metadata associated with the content, can be shared via an approach in which content items maintained in the first repository are synchronized with a copy of the content items maintained in a second repository of a second installation (which can optionally be a cloud-based installation). The first installation can be optionally firewall protected. The copy of the content items can be accessed by collaborative users both within and external to a firewall. Related systems, methods, products, etc. are described.

Abstract: Content maintained in a first repository of a first installation (which can optionally be an on-premise installation) of a content management system, as well as metadata associated with the content, can be shared via an approach in which content items maintained in the first repository are synchronized with a copy of the content items maintained in a second repository of a second installation (which can optionally be a cloud-based installation). The first installation can be optionally firewall protected. The copy of the content items can be accessed by collaborative users both within and external to a firewall. Related systems, methods, products, etc. are described.