RE: SFTP File open modes

[Richard Whalen <Whalenr%process.com@localhost>]

Since both the client and server access files, you can not put the
responsibility for doing conversions on either and "solve" the problem.
Requiring the client to do it means that the client must know about all
possible formats.

You can say that encoding conversions are the responsibility of the reader
(or writer, take your pick) of the file if a common wire format is agreed
upon for certain types of files. (Text in this discussion.)

> -----Original Message-----
> From: nico [mailto:nico%verizon.net@localhost]
> Sent: Friday, March 29, 2002 10:13 PM
> To: Richard Whalen
> Cc: 'ietf-ssh%netbsd.org@localhost'
> Subject: Re: SFTP File open modes
> 
> 
> 
> How many well-known and often utilized ways of encoding ASCII 
> text files
> are there (answer: two)? Is an ASCII mode as you suggest likely to be
> useful? Or do we want a mode for UTF-8 and UTF-16, EBCEDIC, and so on?
> 
> Perhaps it would be best to add an operation by which the 
> client can ask
> the server for a given file's content type and encoding. The server's
> response should indicate whether it knows, whether it knows 
> for certain
> and, if it knows at all, what the content type is.
> 
> All encoding conversions though should be left to the client though.
> 
> IMHO. Cheers,
> 
> Nico
> 
> On Wed, Mar 27, 2002 at 02:36:06PM -0500, Richard Whalen wrote:
> > The current specification of SFTP states that files are 
> always opened in
> > "binary" mode - no translations between different character 
> sets and newline
> > encodings.
> 
> [...]
> 
> > ----------------------
> > Richard Whalen
> > Process Software
> > 508-879-6994
>