Project

General

Profile

Actions

Feature #5630

closed

Missing custom transfer modes in Net::FTP

Added by Lavir_the_Whiolet (Lavir the Whiolet) over 12 years ago. Updated over 10 years ago.

Status:
Rejected
Target version:
[ruby-core:41015]

Description

Net::FTP supports binary and text transfer modes only but some systems support another modes. For example, EBCDIC mode ("TYPE E") in IBM mainframes.

Custom transfer modes are needed to be supported by Net::FTP.

Updated by shugo (Shugo Maeda) over 12 years ago

  • Assignee set to shugo (Shugo Maeda)
Actions #2

Updated by shyouhei (Shyouhei Urabe) about 12 years ago

  • Status changed from Open to Assigned

Updated by shugo (Shugo Maeda) almost 12 years ago

  • Status changed from Assigned to Feedback

Lavir_the_Whiolet (Lavir the Whiolet) wrote:

Net::FTP supports binary and text transfer modes only but some systems support another modes. For example, EBCDIC mode ("TYPE E") in IBM mainframes.

Custom transfer modes are needed to be supported by Net::FTP.

What do you expect for custom transfer modes?

Data types' may be more appropriate than transfer modes' according to RFC959.

I don't have IBM mainframes, so I'm not sure what is needed.

I guess it's not enough to provide a way to send "TYPE E".
With EBCDIC type, is used to denote end-of-line.
Should Net::FTP convert from EBCDIC code to ASCII code?
Ruby doesn't support EBCDIC, so it's pain to directly handle EBCDIC characters.

Actions #4

Updated by mame (Yusuke Endoh) over 11 years ago

  • Target version set to 2.6

Updated by shugo (Shugo Maeda) over 10 years ago

  • Status changed from Feedback to Rejected

I close this issue because there's no feedback for a long time.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0