send package:socket

send :: Socket f t p -> ByteString -> MessageFlags -> IO Int

socket System.Socket

Send data.

Calling send on a closed socket throws eBadFileDescriptor even if the former file descriptor has been reassigned.
The operation returns the number of bytes sent. On Datagram and SequentialPacket sockets certain assurances on atomicity exist and eAgain or eWouldBlock are thrown until the whole message would fit into the send buffer.
This operation throws SocketExceptions. Consult man send for details and specific errors.
eAgain, eWouldBlock and eInterrupted and handled internally and won't be thrown. For performance reasons the operation first tries a write on the socket and then waits when it got eAgain or eWouldBlock.

sendTo :: Family f => Socket f t p -> ByteString -> MessageFlags -> SocketAddress f -> IO Int

socket System.Socket

Like send, but allows to specify a destination address.

sendAll :: Socket f Stream p -> ByteString -> MessageFlags -> IO Int

socket System.Socket.Type.Stream

Sends a whole ByteString with as many system calls as necessary and returns the bytes sent (in this case just the ByteStrings length).

sendAllBuilder :: Socket f Stream p -> Int -> Builder -> MessageFlags -> IO Int64

socket System.Socket.Type.Stream

Sends a whole Builder without allocating ByteStrings. If performance is an issue, this operation should be preferred over all other solutions for sending stream data. The operation allocates a single buffer of the given size on entry and reuses this buffer until the whole Builder has been sent. The count of all bytes sent is returned as there is no other efficient way to determine a Builders size without actually building it.

sendAllLazy :: Socket f Stream p -> ByteString -> MessageFlags -> IO Int64

socket System.Socket.Type.Stream

Like sendAll, but operates on lazy ByteStrings. It uses sendAll internally to send all chunks sequentially. The lock on the socket is acquired for each chunk separately, so the socket can be read from in an interleaving fashion.

unsafeSend :: Socket a t p -> Ptr b -> CSize -> MessageFlags -> IO CInt

socket System.Socket.Unsafe

Like send, but using Ptr and length instead of a ByteString. This function is unsafe. bufPtr must refer to a buffer which size is at least bufSize bytes.

unsafeSendTo :: Socket f t p -> Ptr b -> CSize -> MessageFlags -> Ptr (SocketAddress f) -> CInt -> IO CInt

socket System.Socket.Unsafe

Like sendTo, but using Ptr and length instead of a ByteString. This function is unsafe. bufPtr must refer to a buffer which size is at least bufSize bytes.