Carriage Return / Linefeed = CR/LF
These terms also have a number of different / other ways of being programmed, .. (And depending upon the angle it is being approached – they have different usage, Ie Web-Design, Vs System applications Programming.
Below is some links found connected with GOOGLING this term – CR+LF
#1: http://mc-computing.com/languages/CR_LF.htm
#2: http://www.websiterepairguy.com/articles/os/crlf.html
#3: http://www.acunetix.com/websitesecurity/crlf-injection.htm
That seems to provide enough information to satisfy what CR+LF is – (In terms of coding #1 – defines simply HOW cr/lf is coded) – There is not a comprehensive history about how all this came about. (Might add some more to this later) – The #2: Link does touch on the History very briefly, however is not indepth or definitive.
HISTORY OF CR/LF; Visit ~
#4: http://en.wikipedia.org/wiki/Newline
#5: http://www.rfc-editor.org/EOLstory.txt
NUMBER 5 (#5 – ab0ve) – Very Interesting (If your into this sort of thing) – I have pasted the first two paragraphs below – as this explains in part, EVERYTHING that I wanted to know.
The End-of-Line Story
The ASCII standard for text does not define a unique end-of-line (EOL)
character. Instead, ASCII defines two independent and orthogonal
movements of the print head: Carriage Return (CR) and Line Feed (LF).
(IBM's EBCDIC did not make this mistake; it defined a single New Line
(NL) character.) Early operating system designers had to adopt some
"end-of-line" convention using CR and LF; some used LF, some used
CR, and some used a two-octet sequence: LF CR or CR LF.
During the early ARPAnet research days (~1970-1972), this end-of-line
diversity among operating systems made network communication between
diverse host systems difficult. After some discussion (recorded in
early RFCs), the researchers adopted a single convention:
ASCII text transmitted across the network *must* use the
two-character sequence: CR LF.
The complete page is NOT very big, and well worth a read – (Think Ill go read it NOW!)