ú΄D  The output handle The input filepath The offset to start at The number of bytes to send wraps sendFile' to check arguments   +The length (in bytes) which should be sent )The file offset (in bytes) to start from 1The simplest interface. Simply give it an output  and the  to the input file. The output socket &The path where the input file resides ÿRA more powerful interface than sendFile which accepts a starting offset, and the bytecount to send; the offset and the count must be a positive integer. The initial position of the input file handle matters not since the offset is absolute, and the final position may be different depending on the platform -- no assumptions can be made. The output socket The input file handle The offset to start at The number of bytes to send /The unsafe version of sendFile which accepts a  instead of a P for the output. It will flush the output handle before sending any file data. The output handle &The path where the input file resides The unsafe version of sendFile' which accepts a  instead of a O for the output. It will flush the output handle before sending any file data. The output handle The input filepath The offset to start at The number of bytes to send LReturns the mode that sendfile was compiled with. Mainly for debugging use.  | Possible values are WIN32_SENDFILE, LINUX_SENDFILE, FREEBSD_SENDFILE,  | DARWIN_SENDFILE, and PORTABLE_SENDFILE. )The mode that sendfile was compiled with        sendfile-0.6.1Network.Socket.SendFileNetwork.Socket.SendFile.Linux Network.Socket.SendFile.Internal ByteCountOffsetsendFile sendFile'unsafeSendFileunsafeSendFile' sendFileMode c_sendfile _sendFile rsendfilesendfilemaxBytes sendFile''unsafeSendFile'' wrapSendFile' handleToFdnetwork-2.2.1.7Network.SocketSocketbaseGHC.IOFilePathGHC.IO.Handle.TypesHandle