Socket.Availabl e and UDP datagrams

[Claire]

I'm implementing a UDP server socket from the system.net.sock ets.socket
class. (no, I don't want to use the udpclient class)
I'm polling the socket in a thread, testing the socket.availabl e property on
each pass.
With datagrams, does socket.availabl e only advertise when there are complete
packets in its buffers?
What i mean to say is that if socket.Availabl e > 0 then there will be at
least 1 whole datagram ready to be read? So, if less than a full datagram
arrived, socket.availabl e would return zero?
I've already noticed that if socket.Availabl e is greater than the size of a
single datagram Socket.Read method returns a single datagram leaving the
remainder of the bytes in a buffer ready to be collected with subsequent
calls to socket.read (even if you ask for the whole buffer)
Hoping that someone else will have studied the socket classes' behaviour.
thanks

Example server UDP dotnet socket code
myServerSocket = new Socket(System.N et.Sockets.Addr essFamily.Inter Network,
System.Net.Sock ets.SocketType. Dgram,
System.Net.Sock ets.ProtocolTyp e.Udp);
myServerEndpoin t = new System.Net.IPEn dPoint(System.N et.IPAddress.An y,
12345);
myServerSocket. Bind(myServerEn dpoint);
while(Condition )
{
Available = myServerSocket. Available;
if (Available > 0)
{
foobar();
}
Thread.Sleep(sl eeptime);
}

[Kevin Yu [MSFT]]

Hi Claire,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you need to know if socket.availabl e
only advertise when there are complete packets in its buffers. If there is
any misunderstandin g, please feel free to let me know.

As far as I know, it has to return the size of the first message when a
complete message is available in buffer. According to MSDN, if you are
using a message-oriented socket type such as Dgram, the available data is
the first message in that buffer. If no data is queued in the network
buffer, Available returns 0.

So there are complete messages in buffer, it returns the size of the first
one. Or it returns 0.

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[William Stacey [MVP]]

Unless you have some need not given here, polling like this is very
inefficient for a service. Instead, block on Receive(). The thread will
wait/block until a whole datagram arrives.

--
William Stacey [MVP]

"Claire" <cz*********@co mmunity.nospam> wrote in message
news:ei******** ******@TK2MSFTN GP15.phx.gbl...

I'm implementing a UDP server socket from the system.net.sock ets.socket
class. (no, I don't want to use the udpclient class)
I'm polling the socket in a thread, testing the socket.availabl e property
on each pass.
With datagrams, does socket.availabl e only advertise when there are
complete packets in its buffers?
What i mean to say is that if socket.Availabl e > 0 then there will be at
least 1 whole datagram ready to be read? So, if less than a full datagram
arrived, socket.availabl e would return zero?
I've already noticed that if socket.Availabl e is greater than the size of
a single datagram Socket.Read method returns a single datagram leaving the
remainder of the bytes in a buffer ready to be collected with subsequent
calls to socket.read (even if you ask for the whole buffer)
Hoping that someone else will have studied the socket classes' behaviour.
thanks

Example server UDP dotnet socket code
myServerSocket = new Socket(System.N et.Sockets.Addr essFamily.Inter Network,
System.Net.Sock ets.SocketType. Dgram,
System.Net.Sock ets.ProtocolTyp e.Udp);
myServerEndpoin t = new System.Net.IPEn dPoint(System.N et.IPAddress.An y,
12345);
myServerSocket. Bind(myServerEn dpoint);
while(Condition )
{
Available = myServerSocket. Available;
if (Available > 0)
{
foobar();
}
Thread.Sleep(sl eeptime);
}