Abstract:
Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.
Abstract:
Enterprise administrators in a cloud-based environment including a cloud-based server and a repository can selectively impose permissions on items (e.g., files and folders) marked for synchronization (“sync items”). The sync items can be synchronized with the client devices of users by downloading the items along with the permission attributes from the cloud-based server. However, the permissions on those sync items means that any unpermitted changes to the local copies of the sync items do not get uploaded to the cloud-based server. A synchronization client on the client devices detects any changes made locally to the sync items that are not consistent with the permission attributes, and repairs those changes so that the sync items are restored to their most recent states. This ensures that any unauthorized changes made to sync items remain local and do not propagate by the synchronization process to other users.
Abstract:
Systems and methods for maintaining and updating file system shadows by a synchronization client of a cloud-based platform. In some embodiments, an executor of the synchronization client can execute an action on an item in the local file system which changes the state of the item from an old state to a new state. The synchronization client updates the file system shadows with the new state of the item via an interface to facilitate generation of a synchronization event for the change to the item, that would otherwise go undetected if the change to the item was immediately reversed. In some embodiments, methods for providing shadow consistency and enhancing concurrent access to shadows are implemented by the synchronization client in maintaining and updating the file system shadows.
Abstract:
Systems and methods for maintaining and updating file system shadows by a synchronization client of a cloud-based platform. In some embodiments, an executor of the synchronization client can execute an action on an item in the local file system which changes the state of the item from an old state to a new state. The synchronization client updates the file system shadows with the new state of the item via an interface to facilitate generation of a synchronization event for the change to the item, that would otherwise go undetected if the change to the item was immediately reversed. In some embodiments, methods for providing shadow consistency and enhancing concurrent access to shadows are implemented by the synchronization client in maintaining and updating the file system shadows.
Abstract:
Systems and methods for maintaining and updating file system shadows by a synchronization client of a cloud-based platform. In some embodiments, an executor of the synchronization client can execute an action on an item in the local file system which changes the state of the item from an old state to a new state. The synchronization client updates the file system shadows with the new state of the item via an interface to facilitate generation of a synchronization event for the change to the item, that would otherwise go undetected if the change to the item was immediately reversed. In some embodiments, methods for providing shadow consistency and enhancing concurrent access to shadows are implemented by the synchronization client in maintaining and updating the file system shadows.
Abstract:
Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.
Abstract:
Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.
Abstract:
Systems and methods for maintaining and updating file system shadows by a synchronization client of a cloud-based platform. In some embodiments, an executor of the synchronization client can execute an action on an item in the local file system which changes the state of the item from an old state to a new state. The synchronization client updates the file system shadows with the new state of the item via an interface to facilitate generation of a synchronization event for the change to the item, that would otherwise go undetected if the change to the item was immediately reversed. In some embodiments, methods for providing shadow consistency and enhancing concurrent access to shadows are implemented by the synchronization client in maintaining and updating the file system shadows.
Abstract:
Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.
Abstract:
Enterprise administrators in a cloud-based environment including a cloud-based server and a repository can selectively impose permissions on items (e.g., files and folders) marked for synchronization (“sync items”). The sync items can be synchronized with the client devices of users by downloading the items along with the permission attributes from the cloud-based server. However, the permissions on those sync items means that any unpermitted changes to the local copies of the sync items do not get uploaded to the cloud-based server. A synchronization client on the client devices detects any changes made locally to the sync items that are not consistent with the permission attributes, and repairs those changes so that the sync items are restored to their most recent states. This ensures that any unauthorized changes made to sync items remain local and do not propagate by the synchronization process to other users.