# US 8,543,700 B1 · Asynchronous content transfer > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,543,700 B1 - Document ID: US8543700B1 - Status: Granted - Kind: B1 - Application number: 11/823,608 - Filed: 2007-06-28 - Granted: 2013-09-24 - Earliest claimed: 2007-06-28 - Assignees: EMC Corporation - Applicants: Craig Randall; Alex Rankov; Meir Amiel; Oleg Bivol - Inventors: Craig Randall; Alex Rankov; Meir Amiel; Oleg Bivol - Web page: https://patentgrep.com/patent/US8543700B1 ## CPC - G06F 16/9574: {of access to content, e.g. by caching} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Managing content is disclosed. An indication that a remote host desires to write a content data to a data repository is received. The remote host is caused to transfer the content data to a branch content store that is nearer to the remote host than the data repository is near to the remote host, by a prescribed measure, and that is configured to transfer the content data asynchronously to the data repository. ## Claims ### Claim 1 A method executing on hardware of managing content, comprising: receiving an indication that a remote host desires to write a content data to a data repository, wherein the remote host is caused to transfer the content data nearby in the event the remote host provides an additional indication that the remote host desires the content data to be transferred to the data repository asynchronously; determining a branch content store that is nearer to the remote host than the data repository is near to the remote host, by a prescribed measure; causing the remote host to transfer the content data to the branch content store, wherein the branch content store is configured to transfer the content data asynchronously to the data repository; and making the content data available directly from the branch content store if a request to retrieve the content data from the data repository is received prior to the content data having been transferred asynchronously from the branch content store to the data repository. ### Claim 2 (depends on 1) A method as recited in claim 1, wherein the indication that the remote host desires to write the content data to the data repository is received from the remote host. ### Claim 3 (depends on 1) A method as recited in claim 1, wherein the indication includes an indication that the remote host desires the content to be transferred to the data repository asynchronously. ### Claim 4 (depends on 1) A method as recited in claim 1, wherein the content data is transferred from the remote host directly to the data repository in the event the remote host provides an indication that the remote host desires the transfer to be synchronous. ### Claim 5 (depends on 1) A method as recited in claim 1, wherein causing the remote host to transfer the content data to the branch content store comprising providing to the remote host a URL or other locator associated with a storage location on a host with which the branch content store is associated. ### Claim 6 (depends on 1) A method as recited in claim 1, wherein the indication is received at a service associated with the data repository. ### Claim 7 (depends on 6) A method as recited in claim 6, wherein the service comprises a web service. ### Claim 8 (depends on 6) A method as recited in claim 6, wherein the remote host comprises a consumer process that is a consumer of the service. ### Claim 9 (depends on 1) A method as recited in claim 1, wherein the remote host comprises a content management client configured to transfer the content data to the branch content store. ### Claim 10 (depends on 1) A method as recited in claim 1, wherein the remote host comprises a content management client configured to transfer content to the branch content store or directly to the data repository in response to receiving an instruction indicating a destination to which a particular content is to be transferred. ### Claim 11 (depends on 1) A method as recited in claim 1, further comprising maintaining a distributed content map indicating for each content data associated with the data repository a current location in which a latest version of the content data is stored. ### Claim 12 (depends on 11) A method as recited in claim 11, wherein the current location may be one of a plurality of locations in which the latest version of the content data is stored and the distributed content map indicates each such location. ### Claim 13 (depends on 1) A method as recited in claim 1, wherein the data repository is associated with a content management system. ### Claim 14 (depends on 13) A method as recited in claim 13, wherein the content management system is configured to store a metadata associated with the content data. ### Claim 15 (depends on 1) A method as recited in claim 1, further comprising storing in a metadata store associated with the data repository said metadata associated with the content data. ### Claim 16 (depends on 1) A method as recited in claim 1, wherein the prescribed measure is based at least in part on one or more of the following: geography, geographic distance, communication lag time, network topography, and round trip communication latency.