Re: [PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] PHP EOL
Hello Stuart, After some closer look at the RFC Compliant manuals you suggested, I have determined that the creator of that code was in fact RFC821 Compliant. Being that this was a code I found several years ago, RFC822 may not have been in effect. This being the reason (I believe) that the creator went with a check for System OS when determining the end of line characters to use. Not substantiated in any way, but that is what it looks like to me. I could stand corrected. Best, Karl On Jul 3, 2011, at 6:11 PM, Karl DeSaulniers wrote: I see. Yes, I was referring to the PHP manual. I will investigate the RFC manuals as well like you had noted. No offense taken. Thank you for the clarification. Best, Karl On Jul 3, 2011, at 6:07 PM, Stuart Dallas wrote: On Sun, Jul 3, 2011 at 11:22 PM, Karl DeSaulniers k...@designdrumm.com wrote: @Stuart, Actually that is what made me look into the PHP_EOL Stuart. Wanting to do things right. Did you not read my initial email? I am not suggesting anyone adopt my code. The question was directed to what the differences are so I COULD learn the right way. Being that this was something I got off a tutorial from an accredited website, your saying that to the wrong person. I went and read the manuals and am here now posting the question so as to get the right direction. I have heard the argument and actually agreed. It would be better to use the PHP_EOL instead. I have been directed in the right direction. So I will be changing my code to reflect. I meant no offence, I was simply responding to your comment: Also, It has worked for years with no problem and I would still use it ...and took it to mean you would have no issue with using that code, so I thought it worth pointing out that the standards exist for a reason. In the name of clarification, the manual I was referring to is the sum total of the RFCs that define the various protocols used on the internet, not the PHP manual which I believe you think I meant. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ Karl DeSaulniers Design Drumm http://designdrumm.com Karl DeSaulniers Design Drumm http://designdrumm.com -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] PHP EOL
On Mon, Jul 4, 2011 at 7:11 AM, Karl DeSaulniers k...@designdrumm.comwrote: Hello Stuart, After some closer look at the RFC Compliant manuals you suggested, I have determined that the creator of that code was in fact RFC821 Compliant. Being that this was a code I found several years ago, RFC822 may not have been in effect. This being the reason (I believe) that the creator went with a check for System OS when determining the end of line characters to use. Not substantiated in any way, but that is what it looks like to me. I could stand corrected. RFC821: Simple Mail Transfer Protocol, dated August 1982 ( http://www.faqs.org/rfcs/rfc821.html) RFC822: Standard for the Format of ARPA Internet Text Messages, dated August 13, 1982 (http://www.faqs.org/rfcs/rfc822.html) So, unless you started using that code before PHP was created (1995 if we go back as far as PHP/FI) then no, RFC822 predates that snippet of code. Further, RFC821 defines the end of lines as CRLF, so the creator of that code was not RFC821 compliant if it was being used to send commands to an SMTP server. From RFC821, MAIL FROM command definition: MAIL SP FROM:reverse-path CRLF From RFC822, general header field definition: field = field-name : [ field-body ] CRLF Note the CRLF at the end of both definitions. Now, technically speaking the body of email messages can use any line endings they want to, but the headers should use CRLF, and commands sent to servers should also use CRLF. One final thing for you to consider... what we've been talking about is commands and messages being sent to other computers, so what good does it do to send them in a format that's dependent on the OS of the sending machine? The standards exist so they are OS-independant, because you usually cannot tell what OS the computer you're talking to is running. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/
Re: [PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] Re: [PHP-DB] Re: [PHP] PHP EOL
@Stuart
Ah, then you are right that they were not compliant. The code is not
that old.
Thank you so much for the links and information too. Much more than I
expected.
I did not know that they were sent OS-Independent, but that makes
perfect sense.
Again, please excuse my lack of understanding.
My thought on why I would still use the code was that even though the
SMTP server
would not be OS specific, the email program or browser would be and
that it would format
for the user depending on that program/browser and the OS it runs on.
IE: Thunderbird on PC or Mac Mail; viewing yahoo on Safari Mac or IE
on PC.
Technically speaking, is it not possible to determine with a if {} to
see which catches?
This is probably not the best way to go about formating, just more
for my intuit.
With that code, I did not get any bounce backs or messages pertaining
to ill formatting or no send no show.
So it didn't seem to be a bad code. Thus I continued use.
But like what was said earlier in the thread, I agree PHP_EOL would
be the best fit.
Thank you for all your input, help and resources.
Best,
Karl
On Jul 4, 2011, at 2:01 AM, Stuart Dallas wrote:
On Mon, Jul 4, 2011 at 7:11 AM, Karl DeSaulniers
k...@designdrumm.comwrote:
Hello Stuart,
After some closer look at the RFC Compliant manuals you suggested,
I have determined that the creator of that code was in fact RFC821
Compliant.
Being that this was a code I found several years ago, RFC822 may
not have
been in effect.
This being the reason (I believe) that the creator went with a
check for
System OS when determining the end of line characters to use.
Not substantiated in any way, but that is what it looks like to
me. I could
stand corrected.
RFC821: Simple Mail Transfer Protocol, dated August 1982 (
http://www.faqs.org/rfcs/rfc821.html)
RFC822: Standard for the Format of ARPA Internet Text Messages,
dated August
13, 1982 (http://www.faqs.org/rfcs/rfc822.html)
So, unless you started using that code before PHP was created (1995
if we go
back as far as PHP/FI) then no, RFC822 predates that snippet of code.
Further, RFC821 defines the end of lines as CRLF, so the creator of
that
code was not RFC821 compliant if it was being used to send commands
to an
SMTP server.
From RFC821, MAIL FROM command definition: MAIL SP FROM:reverse-
path
CRLF
From RFC822, general header field definition: field = field-name : [
field-body ] CRLF
Note the CRLF at the end of both definitions.
Now, technically speaking the body of email messages can use any line
endings they want to, but the headers should use CRLF, and commands
sent to
servers should also use CRLF.
One final thing for you to consider... what we've been talking
about is
commands and messages being sent to other computers, so what good
does it do
to send them in a format that's dependent on the OS of the sending
machine?
The standards exist so they are OS-independant, because you usually
cannot
tell what OS the computer you're talking to is running.
-Stuart
--
Stuart Dallas
3ft9 Ltd
http://3ft9.com/
Karl DeSaulniers
Design Drumm
http://designdrumm.com
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
