Hi,
Microsoft can and does send unnaturally large messages. I think UInt64 is fine for CL, but you should be able to set a message limit that is smaller. Also, you may want to accept an incorrect CL, but if it is incorrect by several K, you might close the connection. Finally, I missed why it would be useful to have UInt8 support anywhere.
thanks,
-rohan
On 8/7/06 10:43, "Byron Campen" <bcampen@xxxxxxxxxxxx> wrote:
>I guess I mis-remembered that detail. But, does UInt32 sound like a reasonable limit? Or should we go with UInt64 so file transfers of larger than 4G can be carried out using a single sip request? Is any other implementation on the face of the planet likely to accept a Content-Length this large?
CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain information that is confidential and/or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, please DO NOT disclose the contents to another person, store or copy the information in any medium, or use any of the information contained in or attached to this transmission for any purpose. If you have received this transmission in error, please immediately notify the sender by reply email or at mailto:privacy@xxxxxxxxxxxxxxx, and destroy the original transmission and its attachments without reading or saving in any manner.
Yes, but is "unnaturally large" larger than 4GB? I can cook up a UInt64Category and patch it in, but I want to know whether anyone thinks it will actually be useful. (Which reminds me; I have removed UInt8Parameter and UInt8Category)
Best regards, Byron Campen
|