http://blogs.msdn.com/joncole/archive/2006/04/25/simple-message-framing-sample-for-tcp-socket-part-2-asynchronous.aspxAs a follow up to my last post ( http://blogs.msdn.com/joncole/archive/2006/03/20/555721.aspx ) I decided to add some sample code for implementing an asynchronous version of ReadMessage. All of the same rules apply as discussed in my previous post, buten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/joncole/archive/2006/04/25/simple-message-framing-sample-for-tcp-socket-part-2-asynchronous.aspx#913917Tue, 31 Oct 2006 21:25:39 GMT91d46819-8472-40ad-a661-2c78acb4018c:913917edward<P>Hi, </P> <P>if (state.bytesReceived == 4)//we have received the entire message size information</P> <P>How could you make sure the recieve byte number is less than or equal to 4, if the first time, the count is more than 4, so what will happen?</P> <P>Thanks.</P>http://blogs.msdn.com/joncole/archive/2006/04/25/simple-message-framing-sample-for-tcp-socket-part-2-asynchronous.aspx#1186357Fri, 01 Dec 2006 23:10:21 GMT91d46819-8472-40ad-a661-2c78acb4018c:1186357joncole<p>When the first BeginReceive is started, the buffer passed in is only 4 bytes in size. &nbsp;This means that we can't receive more than 4 bytes, making it possible to use this logic. &nbsp;If we were trying to build a more performant system, we wouldn't use just 4 bytes for the buffer and we would have to check for more than 4 bytes being received. &nbsp;I wrote it this way to simplify the example code for the purposes of this sample.</p>