Specify the maximum number of bytes to buffer before writing to the network. For HTTP and HTTPS, this translates to the maximum HTTP request body size.
In general for HTTP and HTTPS, the larger the buffer size, the fewer the number of HTTP request-response cycles, but the more memory required.
For TCPIP and TLS, it is also the case that a larger size performs faster but requires more memory; however, the performance difference is less significant than for HTTP.
Units are in bytes. Specify K for kilobytes, M for megabytes or G for gigabytes.
The maximum value is 1G.
This option controls the size of the requests from the client and has no bearing on the size of the responses from MobiLink.
For information about how to set network protocol options with dbmlsync, see CommunicationAddress (adr) extended option.
For information about how to set network protocol options with UltraLite, see Network protocol options for UltraLite synchronization streams.
The following example sets the maximum number of bytes to 32K.
On a SQL Anywhere client, the implementation is:
dbmlsync -e "adr=buffer_size=32K"
In an UltraLite application written in embedded SQL or C++, the implementation is:
synch_info.stream_parms = TEXT("buffer_size=32K");
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|