Unified system for connecting a content repository to a file sharing service

1. A method of providing access to repository content, comprising:

receiving, from a client device associated with a user, a revised content associated with a repository content object, wherein the revised content reflects at least in part a modification made to the repository content object;

determining that the revised content is to be stored in the repository, comprising determining how the revised content is to be shared via a file sharing service based at least in part on one or more policies associated with the user and determining whether to publish the revised content to the file sharing service in connection with the synchronized share based at least in part on whether the modification made to the repository content is in the context of a file sharing service to which the repository content object as stored in the repository was published in connection with a synchronized share of the repository object via the file sharing service, wherein at least one of the one or more policies are enforced at an attribute level of content to be shared via the file sharing service, and wherein the determining of how the revised content is to be shared via the file-sharing service comprises determining a manner in which the revised content is to be stored in the repository;

storing the revised content in the repository;

polling the repository for a change to a part of the repository associated with the file sharing service, wherein the repository is a central repository for a plurality of client devices; and

in response to determining that the repository content object was published in connection with the synchronized share of the repository object via the file sharing service and that the revised content is to be published via the file sharing service in connection with the synchronized share, publishing the revised content to the file sharing service in connection with the synchronized share.

2. The method of claim 1 , wherein the revised content is received at least in part by participating in a file sharing service share to which the repository object was published and detecting that the revised content has been stored in connection with the file sharing service share.

3. The method of claim 2 , wherein detecting that the revised content has been stored in connection with the file sharing service share comprises receiving an indication that the revised content has been saved in a share folder with which the file sharing service share is associated.

4. The method of claim 1 , wherein determining that the revised content is to be stored in the repository includes reading a configuration data associated with the synchronized share.

5. The method of claim 4 , wherein the configuration data indicates that changes made in the context of the file sharing service to the repository object are to be propagated to the repository.

6. The method of claim 5 , wherein the configuration data indicates a manner in which changes made to the repository object in the context of the file sharing service are to be propagated to the repository.

7. The method of claim 6 , wherein the indicated manner comprises one or more of the following: an update to a current version of the repository object as stored in the repository; a major version of the repository object as stored in the repository; a minor version of the repository object as stored in the repository; a new repository object; and a clone repository object.

8. The method of claim 1 , wherein publishing the repository object to the file sharing service in connection with the synchronized share includes determining that the repository object is associated with the synchronize share.

9. The method of claim 8 , wherein determining that the repository object is associated with the synchronize share includes determining that the repository object is associated with a repository folder with which the synchronized share is associated.

10. The method of claim 8 , wherein determining that the repository object is associated with the synchronize share includes determining that the repository object includes applying a configuration data to metadata associated with the repository object at the repository to determine that the repository object meets a criteria to be published to the file sharing service in connection with the synchronized share.

11. The method of claim 10 , wherein the criteria includes one or more of the following: the repository object is of an object type indicated in the configuration data; the repository object is in a format indicated in the configuration data; and the repository object has an attribute value that meets an attribute-based criteria in the configuration data.

12. The method of claim 1 , wherein the repository comprises a first repository included in a plurality of repositories with respect to which synchronized sharing is being provided; and wherein storing the revised content in the repository includes providing the revised content via a generic repository interface to a first connector agent associated with the first repository.

13. The method of claim 1 , wherein storing the revised content in the repository comprises using a repository credential of a share user with which the synchronized share is associated to store the revised content in the repository on behalf of the share user.

14. The method of claim 13 , wherein using a repository credential of a share user with which the synchronized share is associated to store the revised content in the repository on behalf of the share user includes using a super user credential to log into the repository as or on behalf of the share user.

15. The method of claim 1 , wherein the determining how the revised content is to be shared is further based at least in part on one or more higher-level policies to which the one or more policies associated with the user are subject.

16. The method of claim 1 , wherein the determining that the revised content is to be stored in the repository further comprises applying a conflict resolution process in the event that a conflict between versions of the repository content object.

17. The method of claim 1 , wherein the determining of how the revised content is to be shared via the file-sharing service comprises determining an extent to which the revised content is to be stored in the repository.

18. The method of claim 1 , wherein the manner in which the revised content is to be stored in the repository is based at least in part on at least one of the one or more policies associated with the user.

19. The method of claim 1 , wherein the determining the manner in which the revised content is to be stored in the repository comprises determining whether the revised content is to be stored so as to overwrite the repository content object.

20. The method of claim 1 , wherein the one or more policies indicate a manner by which the revised content is to be synchronized.

21. The method of claim 20 , wherein the one or more policies indicates whether the revised content is to be synchronized one-way or two-way.

22. A system to provide access to repository content, comprising:

a communication interface; and

a processor coupled to the communication interface and configured to:

receive, from a client device associated with a user, via the communication interface a revised content associated with a repository content object, wherein the revised content reflects at least in part a modification made to the repository content object;

determine that the revised content is to be stored in the repository, comprising determining how the revised content is to be shared via a file sharing service based at least in part on one or more policies associated with the user and determining whether to publish the revised content to the file sharing service in connection with the synchronized share based at least in part on whether the modification made to the repository content is in the context of a file sharing service to which the repository content object as stored in the repository was published in connection with a synchronized share of the repository object via the file sharing service, wherein at least one of the one or more policies are enforced at an attribute level of content to be shared via the file sharing service, and wherein the determining of how the revised content is to be shared via the file-sharing service comprises determining a manner in which the revised content is to be stored in the repository;

store the revised content in the repository;

poll the repository for a change to a part of the repository associated with the file sharing service, wherein the repository is a central repository for a plurality of client devices; and

in response to determining that the repository content object was published in connection with the synchronized share of the repository object via the file sharing service and that the revised content is to be published via the file sharing service in connection with the synchronized share, publish the revised content to the file sharing service in connection with the synchronized share.

23. The system of claim 22 , wherein the processor executes computer instructions to provide a connection engine to receive the revised content and provide the revised content to a connector agent associated with the repository.

24. The system of claim 23 , wherein the processor executes computer instructions to provide the connector agent; and wherein the connector engine determines based at least in part on a synchronization profile that the revised content is to be stored in the repository.

25. The system of claim 24 , wherein the synchronization profile indicates a manner in which the revised content is to be stored in the repository.

26. A computer program product to provide access to repository content, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:

receiving, from a client device associated with a user, a revised content associated with a repository content object, wherein the revised content reflects at least in part a modification made to the repository content object;

determining that the revised content is to be stored in the repository, comprising determining how the revised content is to be shared via a file sharing service based at least in part on one or more policies associated with the user and determining whether to publish the revised content to the file sharing service in connection with the synchronized share based at least in part on whether the modification made to the repository content is in the context of a file sharing service to which the repository content object as stored in the repository was published in connection with a synchronized share of the repository object via the file sharing service, wherein at least one of the one or more policies are enforced at an attribute level of content to be shared via the file sharing service, and wherein the determining of how the revised content is to be shared via the file-sharing service comprises determining a manner in which the revised content is to be stored in the repository;

storing the revised content in the repository;

polling the repository for a change to a part of the repository associated with the file sharing service, wherein the repository is a central repository for a plurality of client devices; and

in response to determining that the repository content object was published in connection with the synchronized share of the repository object via the file sharing service and that the revised content is to be published via the file sharing service in connection with the synchronized share, publishing the revised content to the file sharing service in connection with the synchronized share.