🚀 go-pugleaf

"Jeremy" <jeremy@none.com> wrote in message
news:41dd4e96$1@newsgroups.borland.com...

> Whenever I try to send something over my socket, I get
> the following error on the server side:

    WSAENOTCONN
    (10057)

    Socket is not connected.

    A request to send or receive data was disallowed because the socket is
not connected and (when sending on a datagram socket using sendto) no
address was supplied. Any other type of operation might also return this
error - for example, setsockopt setting SO_KEEPALIVE if the connection has
been reset.

> On the client side, I get the following error message:

    WSAECONNABORTED
    (10053)

    Software caused connection abort.

    An established connection was aborted by the software in your host
machine, possibly due to a data transmission timeout or protocol error.

> I'm fairly certain that the socket is connected since the
> OnConnect events occur for both the client and the server.

The problem is that your sockets are being disconnected abnormally.

> Am I using the ReceiveText function incorrectly?

Yes.  See below.

> void __fastcall TForm1::ServerSocket1ClientRead(TObject *Sender,
>       TCustomWinSocket *Socket)
> {
>     Edit1->Text = Form1->ServerSocket1->Socket
>                        ->ReceiveText();
> }

That is not correct.  You are accessing the wrong socket entirely.  The code
should be using the event handler's Socket parameter instead:

    void __fastcall TForm1::ServerSocket1ClientRead(TObject *Sender,
TCustomWinSocket *Socket)
    {
        Edit1->Text = Socket->ReceiveText();
    }


Gambit