Re: Read Socket data on data, not return

in reply to Read Socket data on data, not return

It seems more likely that the server you're connecting to is not actually sending the data until a carriage return is issued there. In other words, no matter how your client tries to read the data, it can only get anything if the server has actually written a packet to the socket. Depending on how the socket is being used in the server, the data may be buffered and may not actually be written to the underlying socket until a carriage return is issued.

Can you post some example server code?

Comment on Re: Read Socket data on data, not return

Replies are listed 'Best First'.
Re^2: Read Socket data on data, not return by ecuguru (Monk) on Dec 23, 2004 at 02:40 UTC
The entire server working code is in the first link: here I'm only using telnet as the client, which is sending in every character. client = telnet localhost 2323 thanks!!	[reply]
Re^3: Read Socket data on data, not return by steves (Curate) on Dec 27, 2004 at 02:00 UTC
Does your local telnet client tell you it's operating in character and not line mode? telnet can operate in either. I find that when I connect to non-telnet servers, my telnet client is in line mode, which would explain why your server is "waiting" for newlines -- it's actually only seeing full lines from the client, not characters. To see your telnet client's current mode, escape into telnet command mode and issue the status command.	[reply]

In Section Seekers of Perl Wisdom