Click here to Skip to main content
15,897,718 members

Comments by Yandy Zaldivar (Top 2 by date)

Yandy Zaldivar 20-Mar-14 1:56am View    
Question edited, read after [Edited].
Yandy Zaldivar 19-Mar-14 19:52pm View    
The Socket.SendPacketAsync is the .NET equivalent to the native Windows API function TransmitFile (http://msdn.microsoft.com/en-us/library/windows/desktop/ms740565%28v=vs.85%29.aspx). The TransmitFile function transmits file data over a connected socket handle. This function uses the operating system's cache manager to retrieve the file data, and provides high-performance file data transfer over sockets. I am particularly interested in benefit from this high-performance file data transfer and not in buffering the data myself as you suggest. While the TransmitFile Windows API function allow 64bit offsets, the .NET equivalent is restricted to a 32bit offset. So my question is why is this restriction on .NET?