Bernie Bright writes:
SGSocket::readline() and SGSocket::read() do act differently. For a
server, readline() correctly handles the accept and reads from the new
socket. read() also handles the accept but reads from the master socket.
I'm not sure if this is intentional or if its a bug.
Curtis L. Olson writes:
Bernie Bright writes:
SGSocket::readline() and SGSocket::read() do act differently. For a
server, readline() correctly handles the accept and reads from the new
socket. read() also handles the accept but reads from the master socket.
I'm not sure if this is
On Thu, 27 Nov 2003 07:23:30 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
Curtis L. Olson writes:
Bernie Bright writes:
SGSocket::readline() and SGSocket::read() do act differently. For a
server, readline() correctly handles the accept and reads from the new
socket. read() also
I have done some extensive testing with read() using tcp and it seems to
be working great.
Thanks,
Seamus
On Fri, 28 Nov 2003, Bernie Bright wrote:
On Thu, 27 Nov 2003 07:23:30 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
Curtis L. Olson writes:
Bernie Bright writes:
On Wed, 26 Nov 2003 16:59:53 -0700
Seamus Thomas Carroll [EMAIL PROTECTED] wrote:
Hi,
I am trying to recieve a message using SGSocket::read.
SGSocket::read returns zero bytes read until about the time
I am expecting the first message to be recieved. From here on
SGSocket::read returns
I output the error and I am getting:
Transport endpoint is not connected
The strange part is if I put '\n' at the end of the message and read with
'readline' the message is successfully recieved.
Is this a problem with 'read'?
Seamus
On Thu, 27 Nov 2003, Bernie Bright wrote:
On Wed, 26 Nov
On Wed, 26 Nov 2003 18:04:50 -0700
Seamus Thomas Carroll [EMAIL PROTECTED] wrote:
I output the error and I am getting:
Transport endpoint is not connected
From man recv
ENOTCONN
The socket is associated with a connection-oriented protocol and
has not been
