1.3.2 Message Flow for Upload Mode

In this mode, the request entity is uploaded to the server. Figure 1 (section 1.3) explains this mode of operation in detail.

  1. Steps 1 through 5, described in section 1.3.1, are executed.

  2. After the final FRAGMENT message is processed successfully by the server, the request entity is reassembled at the server. Depending on the notification options (section 3.2.1.1) (NotificationType and NotificationURL) defined on the back-end client, the back-end client can send the request entity to the server application provided through the notificationURL. This step is needed ONLY if the back-end server needs to be notified about the request entity and is not necessary for a simple upload.

  3. After the server sends a success Ack response to the final FRAGMENT message, the client sends a CLOSE-SESSION (section 2.2.8) message, which prompts the server to move the request entity to the destination URL and delete BITS session data for the given session on the server.