1.3.1 Message Flow Common to Both Modes

  • Article

The following steps describe the message flow process that is common to both modes of operation.

The client gets the request entity and the destination URL through the higher-layer protocol.

  1. The client initiates the upload by sending a CREATE-SESSION (section 2.2.2) message, which prompts the server to create a BITS session for the destination URL.

  2. After the BITS session is created, the server sends a BITS session ID through an Ack response (section 2.2.3).

  3. After the client determines that the BITS session creation was successful, it sends the request entity in a set of FRAGMENT (section 2.2.6) messages to the server. For each fragment being sent from the client, the server processes and updates its copy of the request entity.

  4. After the FRAGMENT (section 2.2.6) is successfully received and processed, the server sends Ack (section 2.2.7) with the byte range received.