Carriage Return Problem

jlutz

Hello,

I searched around a bit trying to find a script that will interface with an SNPP server, but was unable to find one, therefore I moved forward in trying to make a basic one on my own. It was going very well until I ran into problems inserting a carriage return at the end of each line. For some reason, it will not have the same effect as me pushing Enter on my computer. Can someone help me out with a suggestion, or solution?

Code:
<?php
$fp = fsockopen("68.46.171.26",444,$errno,$errstr, 10);
if (!$fp) {
echo "$errstr ($errno)<br />\n";
} else {
$out = "PAGE 101\r\n";
$out .= "MESS TEST PAGE\r\n";
$out .= "SEND\r\n";
$out .= "QUIT\r\n";
fputs($fp, $out);
while (!feof($fp)) {
echo fgets($fp, 128);
}
fclose($fp);
}
?>

Also, please note that rather than making variables since Im still testing the script, I just hard-coded their values. I do intend to correct this, before anyone makes any comments about that. 🙂

Thanks in advance for any help,
Joe

mhalloran

Most likely you are sending the browser new lines ( \n ) when it needs a <br> tag for a new line. There is a funciton for this called new line to break:
nl2br()

echo nl2br(fgets($fp, 128));

that should work for ya

yelvington

So often it looks like a PHP problem but turns out to be simple HTML.

<pre>output preformatted text </pre>

jlutz

The problem doesnt lie in returning the information to the browser, in fact I really could care less about returning anything to the browser. What I want to do is make it send the information to the socket connection, and make new lines after each line of text I send. Basically its like Telnet, without the Telnet.

xmatthawkx

I've been experimenting with sockets and testing my script out via telnet to the port i'm binding to, and I noted that line breaks are interpreted incorrectly by the client.

If your telnet client is displaying your data all weird, it isn't necessarly indicative of what your actual snpp server will see. The data is there, the telnet client just doesn't see it correctly.

...at least that's what I've noticed.