> It also makes me curious where the values for MAX_PAYLOAD_SIZE and
> MAX_MESSAGE_SIZE come from? Also, if we could be happy with
> CURL_MAX_WRITE_SIZE sized buffer we could aavoid the extra allocations in
> smb.c compeletely! They are a bit disturbing since we already alloc two 16K
> buffers that are just wasted when SMB is used.

SMB1 limits the payload size to 64K, but I set MAX_PAYLOAD_SIZE to 32K to be on the safe side. The allocation is dynamic, so it only happens if the user actually uses SMB.

-Bill

________________________________

This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-12-08