184.108.40.206 Processing ROPs Asynchronously
Some ROPs can be processed asynchronously. During asynchronous processing, the client receives a RopProgress ROP response buffer ([MS-OXCROPS] section 220.127.116.11) instead of the ROP response buffer that corresponds to the ROP request buffer that the client sent. The RopProgress ROP response indicates that the operation is still being processed. When processing is complete, the client receives the ROP response buffer that corresponds to the original ROP request buffer.
Any of the following ROPs can be processed asynchronously if its ROP request buffer was sent with the WantAsynchronous field set to nonzero (TRUE).
RopMoveCopyMessages (section 18.104.22.168)
RopMoveFolder (section 22.214.171.124)
RopCopyFolder (section 126.96.36.199)
RopEmptyFolder (section 188.8.131.52)
RopHardDeleteMessagesAndSubfolders (section 184.108.40.206)
RopDeleteMessages (section 220.127.116.11)
RopHardDeleteMessages (section 18.104.22.168)
The client can send a RopProgress ROP request buffer either to abort an in-progress operation or to get information about the progress of an operation. For more details about the RopProgress ROP, see [MS-OXCPRPT] sections 2.2.23 and 22.214.171.124.