1.3.3 Message Flow for Upload-Reply Mode

  • Article

In this mode, the server sends the request entity to the server application, which constructs a response entity. The server application sends the URL of the reply to the client as part of the response to the final FRAGMENT sent from the client. The following steps, along with the diagram in section 1.3, explain this mode of operation in detail.

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

  2. After the final FRAGMENT (section 2.2.6) message is processed successfully by the server, the server sends the path to the request entity to the back-end client.

  3. The back-end client sends the request entity to the server application provided through the notificationURL.

  4. The server application sends a reply URL to the back-end client. The back-end client sends this information to the server. The server sends this information to the client as part of a header in the Ack (section 2.2.7) response for the final FRAGMENT message.

  5. The client passes the reply URL to the higher-layer protocol. The download of the reply URL by the higher-layer protocol is beyond the scope of this document.

  6. 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.