> It seems that one of the basic questions here is "Who is responsible > for determining the mode of transfer under ftp, the server or the > client?". My understanding is that it has always been the client. John Junod's (Ipswitch, Inc.) WS_FTP is a handy ftp client for Windows. FWIW, WS_FTP can be set by the user to transfer either by ascii or binary to "view" a file. (My memory of the standard ftp shipped with SunOS is that it acts the same.) Why I bring up WS_FTP is that whether the file is transfered by ascii or binary, in both cases an extra line is not inserted when using the "view" command. In both cases, it appears in memopad (not sure of the English name) as exactly three lines with no intervening blank lines. WS_FTP is making a decision as a client not to add a blank line. Perhaps ascii data and binary data are interpreted independently. __Henry ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
- Re: lynx-dev Revised patch for HTFTP.c Klaus Weide
- Re: lynx-dev Revised patch for HTFTP.c pg
- Re: lynx-dev Revised patch for HTFTP.c pg
- Re: lynx-dev Revised patch for HTFTP.c David Woolley
- Re: lynx-dev Revised patch for HTFTP.c Doug Kaufman
- Re: lynx-dev Revised patch for HTFTP.c David Woolley
- Re: lynx-dev Revised patch for HTFTP.c pg
- Re: lynx-dev Revised patch for HTFTP.c Doug Kaufman
- Re: lynx-dev Revised patch for HTFTP.c Henry Nelson
- Re: lynx-dev Revised patch for HTFTP.c Mike Castle
- Re: lynx-dev Revised patch for HTFTP.c David Woolley
- Re: lynx-dev Revised patch for HTFTP.c Thomas Dickey
- Re: lynx-dev Revised patch for HTFTP.c Mike Castle
- Re: lynx-dev Revised patch for HTFTP.c Doug Kaufman
- Re: lynx-dev Revised patch for HTFTP.c Thomas Dickey
- Re: lynx-dev Revised patch for HTFTP.c Klaus Weide
- Re: lynx-dev Revised patch for HTFTP.c Doug Kaufman
- Re: lynx-dev Revised patch for HTFTP.c pg
- Re: lynx-dev Revised patch for HTFTP.c Wesley Morgan
