commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arno Unkrig (JIRA)" <>
Subject [jira] Commented: (NET-171) Improve
Date Tue, 13 Nov 2007 20:14:42 GMT


Arno Unkrig commented on NET-171:

Hi Rory and Henrik,

I was not aware of Henrik's MVS improvements for 2.0. Indeed they are exactly what I need!
(Hence the overlap is total ;-) Actually, Henrik's implementation is much more complete since
his understanding of the MVS file system mess is much more complete than mine. I more or less
hacked the MVS FTP server behavior.

Henrik surely agrees that the 1.4.1 MVS parser is totally broken.

The only point where the solution that Henrik and Steve developed seems a bit too complicated
is that they define SEVERAL parsers for the several listing formats of the MVS server, and
a strategy to choose one of those. In contrast, I provide only ONE parser class that detects
and parses ALL possible MVS listings. In other words: It is arguable whether the N listing
formats should be parsed by N parser classes, or if the listing formats produced by the ONE
server system MVS should be parsed by ONE parser class. But I'm not the net.commons expert,
and I'd be happy to replace my home-grown MVS solution with the net.commons 2.0.

When will 2.0 be released? I cannot find a roadmap or anything. On the web site, everything
is 1.4.1.



> Improve
> ------------------------------
>                 Key: NET-171
>                 URL:
>             Project: Commons Net
>          Issue Type: Improvement
>         Environment: MVS FTP server
>            Reporter: Arno Unkrig
>         Attachments:,,,
> Hi there,
> the "MVSFTPEntryParser" who parses the output of an FTP LIST of an MVS FTP server, is
a sad view... it's totally broken. I developed a custom FTPEntryParser, which I can hook into
the FtpClient (thank you for the highly customizable design). I'd like to donate it to COMMONS
NET... who can I turn to?
> CU
> Arno Unkrig

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message