Download acknowledgement is not required to ensure that your data is received at the remote.

There are two modes of download acknowledgement: blocking, which has been deprecated, and non-blocking. Non-blocking is the default. There is a performance penalty for using blocking download acknowledgement: the non-blocking mode is recommended.

To use download acknowledgements, there are settings on both the client and server.

On the client, you specify download acknowledgement with the dbmlsync extended option SendDownloadACK or the UltraLite synchronization parameter Send Download Acknowledgement. If you do not change any settings on the server, the default is non-blocking download acknowledgement.

On the server, you can set the mlsrv11 -nba option to specify blocking download acknowledgement. There are two connection events that you can use to record the last successful download time in your consolidated database when using non-blocking download acknowledgement.

See also

• publication_nonblocking_download_ack connection event
• nonblocking_download_ack connection event
• -nba option
• dbmlsync: SendDownloadACK (sa) extended option
• UltraLite: Send Download Acknowledgement synchronization parameter