🚀 go-pugleaf

I will post code first thing tomorrow.

> Then your failing application is not actually receiving any data from the
> embedded server to begin with, despite what Ethereal says.  Ethereal sits 
> at
> a very low level.  Just because it says data is arriving at the TCP/IP 
> layer
> does not necessary mean that the data is reaching the application layer.

I agree, but the old example chat program works using the same TClientSocket 
component and nearly identical code.  Very strange!





"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4508a3f3$2@newsgroups.borland.com...
>
> "Josh Arnold" <jdaudio02@hotmail.com> wrote in message
> news:4508a026@newsgroups.borland.com...
>
>> I can see the response when capturing with Ethereal. But the OnRead
>> event does not fire in my client app therefore  my application never
>> sees any of the responses from the server.
>
> Please show your actual code.  The only way you would not be receiving the
> event is if the TClientSocket never received the notification in the first
> place.  Since non-blocking sockets use the message queue, make sure that 
> you
> are not using anything that can discard messages before they are 
> processed.
>
>> I can run the Internet Chat example program from C++ Builder 5 on
>> another machine and my app talks to it and receives from it just fine.
>> AND I can use the Chat example program to talk to the embedded
>> server device and it WILL see the responses from the server.  Both
>> applications use the same TClientSocket component.
>
>
>
> Gambit
>
>