Feature #5630

Missing custom transfer modes in Net::FTP

Added by Lavir the Whiolet over 2 years ago. Updated 6 months ago.

[ruby-core:41015]
Status:Rejected
Priority:Normal
Assignee:Shugo Maeda
Category:-
Target version:next minor

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.

History

#1 Updated by Shugo Maeda over 2 years ago

  • Assignee set to Shugo Maeda

#2 Updated by Shyouhei Urabe about 2 years ago

  • Status changed from Open to Assigned

#3 Updated by Shugo Maeda about 2 years ago

  • Status changed from Assigned to Feedback

LavirtheWhiolet (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 thantransfer 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.

#4 Updated by Yusuke Endoh over 1 year ago

  • Target version set to next minor

#5 Updated by Shugo Maeda 6 months ago

  • Status changed from Feedback to Rejected

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

Also available in: Atom PDF