Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!lth.se!newsuser
From: e85rw@efd.lth.se (Ricard Wolf)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Question about Socket
Message-ID: <1990Nov29.075002.6996@lth.se>
Date: 29 Nov 90 07:50:02 GMT
References: <33562@netnews.upenn.edu> <ENAG.90Nov29005054@hild.ifi.uio.no>
Sender: newsuser@lth.se (LTH network news server)
Reply-To: e85rw@efd.lth.se (Ricard Wolf)
Organization: Lund Institute of Technology, Sweden
Lines: 33

In article <ENAG.90Nov29005054@hild.ifi.uio.no> enag@ifi.uio.no (Erik Naggum) writes:
>In article <33562@netnews.upenn.edu>, Menq J. Lee writes:
....
>
>   I have no problem in handling binary transfer. But when it comes to
>   ascii transfer, the reference I read told me that I must take care
>   of some critical cases. Specifically, I have to do some conversion
>   between
>
>		   newline <---> CR,LF     (Carriage Return, Line Feed)
>		   CR <---> CR,NULL
>
>   I have the following questions about this issue:
>
>	   1. Why is this necessary? In other words, under what
>	      situations will this conversion be employed to avoid
>	      foreseeable errors?
>
>It is necessary because you want to relieve your client under operating
>system X from knowing about the line termination conventions of
>operating system Y.  This becomes progressively more pressing for large
>sets of operating systems and conventions.

If you use FTP in the ascii transfer mode (whcih is the default) this is
taken care of automagically.

-- 
Ricard Wolf

+--------------------------+-------------------------------------+
| Ricard Wolf              | Lund Institute of Technology        |
| email: e85rw@efd.lth.se  | If you can't buy 'em - build 'em !! |
+--------------------------+-------------------------------------+