Re: unexpected characters in TCP-communication
- From: Chris Dunaway <dunawayc@xxxxxxxxx>
- Date: Thu, 27 Mar 2008 07:18:12 -0700 (PDT)
On Mar 27, 8:58 am, Peter Pippinger <peter.pippin...@xxxxxx> wrote:
Hello NG,
First of all, have i understood it right,
- that i say in the first byte of the string - i want to send - the
number of chars, that i will send?
- that the fist byte of a string - i recieve - declares the number of
chars, i´ll get?
No, I don't believe this is correct. When sending an array of bytes,
the entire array is sent so there is no need to specify the number of
bytes to send in the array.
When receiving, the return value from the Receive command indicates
the number of bytes received.
.
- Follow-Ups:
- Re: unexpected characters in TCP-communication
- From: Peter Duniho
- Re: unexpected characters in TCP-communication
- From: Peter Pippinger
- Re: unexpected characters in TCP-communication
- References:
- unexpected characters in TCP-communication
- From: Peter Pippinger
- unexpected characters in TCP-communication
- Prev by Date: Re: PresentationFramework Assembly location
- Next by Date: RE: C# equivalent to VB expression
- Previous by thread: unexpected characters in TCP-communication
- Next by thread: Re: unexpected characters in TCP-communication
- Index(es):
Relevant Pages
|