Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!cert!netnews.upenn.edu!grad1.cis.upenn.edu!menqjuh
From: menqjuh@grad1.cis.upenn.edu (Menq J. Lee)
Newsgroups: comp.protocols.tcp-ip
Subject: Question about Socket
Message-ID: <33562@netnews.upenn.edu>
Date: 27 Nov 90 22:52:43 GMT
Sender: news@netnews.upenn.edu
Reply-To: menqjuh@grad1.cis.upenn.edu (Menq J. Lee)
Organization: University of Pennsylvania
Lines: 23

Hi everybody,

I am new to this field, and I am using DGRAM Socket (UDP) to build a remote
copy utility. This utility supports both ascii and binary file transfers.

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?

	2. Do I have to do the same conversion if I use STREAM Socket (TCP) 
	   instead of DGRAM Socket?

Any help will be highly appreciated.

--Menq