2.5.4.4.1.2 Main Success Scenario

  1. The user requests the application to read a file.

  2. The application obtains content identifiers by using one of the access mechanisms as described in section 2.5.4.3.

  3. The content client computes segment identifiers (HoHoDk) for the data.

  4. The content client queries the hosted cache server for the availability of blocks from the target segments by using the Peer Content Caching and Retrieval: Retrieval Protocol as described in [MS-PCCRR].

  5. The hosted cache server indicates that it does not have the required blocks as described in [MS-PCCRR].

  6. The content client retrieves the content from the content server by using the mechanism as described in [MS-FASOD].

  7. The retrieved data is placed in the local cache of the content client computer.

  8. The content client retrieves the data from the local cache and returns it to the application.

  9. The application delivers the file contents to the user.

  10. The content client offers the metadata content to the hosted cache server as described in [MS-PCHC].

  11. The hosted cache server optionally authenticates the content client.

  12. The retrieved data is placed in the distributed cache of the content client computer.

  13. The hosted cache server requests from the content client any required segments and blocks as described in [MS-PCCRR].

  14. The content client sends the requested segments and blocks to the hosted cache server as described in [MS-PCCRR].