in reply to Read and write to socket

The probable answer is "there is a bug in your server", but as you didn't show us that code, we'd only be guessing if we told you where it was ;)


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^2: Read and write to socket
by msalerno (Beadle) on Oct 17, 2007 at 01:00 UTC
    I didn't think it was necessary since the exchange works perfectly when I do it manually using telnet. The server code part is working as expected, it's printing to a socket with the above code that I am asking about.