Re: Strange problem drive me mad.

From: Alexander Nickolov (agnickolov_at_mvps.org)
Date: 12/25/04 

Date: Fri, 24 Dec 2004 17:05:25 -0800

Not through the TCP protocol. You can design your
own packetization on top of TCP, though. 

-- 
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Steven Tang" <steven.tang@tlvsys.com> wrote in message 
news:eCHrJMf6EHA.3236@TK2MSFTNGP15.phx.gbl...
>I found the problem was caused client side recv aggregated the all
> data to one. Is it possible to deny this kind of aggregate?
>
> Regards
> Steven
>
> "Steven Tang" <steven.tang@tlvsys.com> wrote in message 
> news:eHL7pCa6EHA.2012@TK2MSFTNGP15.phx.gbl...
>> Hi All,
>>   I'm being bothered by one very strange socket problem. I created one 
>> server
>> and one client with TCP winsock, I forwarded both ASync events to their 
>> window.
>> and I handle traffic behaviour inside notifination message.
>>  What I want to do is: when server get one message data from client, it 
>> send
>> back 10 buffers data to client. the server code look like these:
>>
>>   for ( int i = 0; i < 10; i ++ ) {
>>        ....
>>        int lenPack =  length of the buffer i
>>        int iRetLen = send( clisock, Number i data buffer, , 0 );
>>        OutputDebugMsg( iRetLen,  lenPack, \n );
>>   }
>>
>>  The client side is just receive the data in the notification message.
>>
>>  when I run server and the client, the client shows only got one data 
>> packet
>> from the server.
>>  when I run the client, line by line trace the above code in server side. 
>> the
>> client shows it got all 10 data packets.
>>  I added some traces code to the server and the client then run them 
>> automatically,
>> the server side debug message terminal shows all ten data are send out 
>> successfully
>> ( iRetLen == lenPack every time). while at client side, the terminal 
>> shows
>> the client only get one notification message.
>>
>> Any comments are very appreciated.
>>
>> Regards
>> Steven
>>
>
>

Relevant Pages

  • Re: Netzwerkproblem GBit -> 100MBit
    ... GBit-Kette - flow control zwingend notwendig sei. ... zwischen Client und Server. ... Das kann TCP an der Stelle nicht mehr leisten. ...
    (de.comp.sys.novell)
  • Re: Log Out Issues
    ... UDP is the way to go for internet games. ... Apparently the extra overhead in TCP can cause a lot more lag in your game, ... >> Lets say the client sends a log out request to the server reliably. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Log Out Issues
    ... your perormance may be worse than TCP. ... would be if your protocol anticipates packet loss and does not ... >>> Lets say the client sends a log out request to the server reliably. ...
    (microsoft.public.win32.programmer.networks)
  • Re: [2.6.24.3][net] bug: TCP 3rd handshake abnormal timeouts
    ... server via TCP and non-persistent connections and all application level ... "Sometimes" when establishing a TCP connection to the server, ... Here is a simplified version of what _both_ the server and the client ...
    (Linux-Kernel)
  • Re: [2.6.24.3][net] bug: TCP 3rd handshake abnormal timeouts
    ... server via TCP and non-persistent connections and all application level ... "Sometimes" when establishing a TCP connection to the server, ... Here is a simplified version of what _both_ the server and the client ...
    (Linux-Kernel)