Socket.BeginReceiveFrom Method (Byte, Int32, Int32, SocketFlags, EndPoint, AsyncCallback, Object)
Begins to asynchronously receive data from a specified network device.
Assembly: System (in System.dll)
[<HostProtectionAttribute(SecurityAction.LinkDemand, ExternalThreading = true)>] member BeginReceiveFrom : buffer:byte * offset:int * size:int * socketFlags:SocketFlags * remoteEP:EndPoint byref * callback:AsyncCallback * state:Object -> IAsyncResult
The zero-based position in the buffer parameter at which to store the data.
The number of bytes to receive.
An object that contains state information for this request.
buffer is null.
remoteEP is null.
An error occurred when attempting to access the socket. See the Remarks section for more information.
offset is less than 0.
offset is greater than the length of buffer.
size is less than 0.
size is greater than the length of buffer minus the value of the offset parameter.
The Socket has been closed.
A caller higher in the call stack does not have permission for the requested operation.
Themethod starts asynchronously reading connectionless datagrams from a remote host. Calling the method gives you the ability to receive data within a separate execution thread.
You can create a callback method that implements the AsyncCallback delegate and pass its name to the method. To do this, at the very minimum, your state parameter must contain the connected or default Socket being used for communication. If your callback needs more information, you can create a small class to hold the Socket and the other required information. Pass an instance of this class to the method through the state parameter.
Your callback method should invoke the EndReceiveFrom method. When your application calls , the system will use a separate thread to execute the specified callback method, and it will block on EndReceiveFrom until the Socket reads data or throws an exception. If you want the original thread to block after you call the method, use WaitHandle.WaitOne. Call the Set method on a T:System.Threading.ManualResetEvent in the callback method when you want the original thread to continue executing. For additional information on writing callback methods, see Marshaling a Delegate as a Callback Method.
This method reads data into the buffer parameter, and captures the remote host endpoint from which the data is sent. For information on how to retrieve this endpoint, refer to EndReceiveFrom. This method is most useful if you intend to asynchronously receive connectionless datagrams from an unknown host or multiple hosts. In these cases, will read the first enqueued datagram received into the local network buffer. If the datagram you receive is larger than the size of buffer, the method will fill buffer with as much of the message as is possible, and throw a SocketException. If you are using an unreliable protocol, the excess data will be lost. If you are using a reliable protocol, the excess data will be retained by the service provider and you can retrieve it by calling the method with a large enough buffer.
To guarantee that the remote host endpoint is always returned, an application should explicitly bind the Socket to a local endpoint using the Bind method and then call the SetSocketOption method with the optionLevel parameter set to IP or IPv6 as appropriate, the optionName parameter set to PacketInformation, and the optionValue parameter to enable this option before calling the method. Otherwise, it is possible for the remote host endpoint to not be returned when the sender has sent a number of datagrams before the receiver has called the method.
Although Connect / BeginConnect method or accept an incoming connection request by calling the Accept or BeginAccept method. If you call the method before establishing or accepting a connection, you will get a SocketException. You can also establish a default remote host for a connectionless protocol prior to calling the method. In either of these cases, the method will ignore the remoteEP parameter and only receive data from the connected or default remote host.is intended for connectionless protocols, you can use a connection-oriented protocol as well. If you choose to do so, you must first either establish a remote host connection by calling the
With connection-oriented sockets,will read as much data as is available up to the number of bytes specified by the size parameter.
To cancel a pending Close method., call the
If you receive a SocketException, use the SocketException.ErrorCode property to obtain the specific error code. After you have obtained this code, refer to the Windows Sockets version 2 API error code documentation in the MSDN library for a detailed description of the error.
This member outputs trace information when you enable network tracing in your application. For more information, see Network Tracing in the .NET Framework.
The execution context (the security context, the impersonated user, and the calling context) is cached for the asynchronous Socket methods. After the first use of a particular context (a specific asynchronous Socket method, a specific Socket instance, and a specific callback), subsequent uses of that context will see a performance improvement.
Available since 1.1