commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Cohen" <>
Subject RE: questions about FTP LIST processing (FTPFileListParser)
Date Thu, 11 Dec 2003 15:33:20 GMT
Jeffrey, I'm soon to be laid off and will have a little time on my
hands.  I would like to take a look at cleaning some of this up.  I
wrote a bug yesterday against the docs which are not totally correct.

Additionally, there has suddenly been a lot of grumbling over at the Ant
site over the FTP task and the impossibility of getting a non-unix
parser using ant's <ftp> task so there is good small bundle of issues to

-----Original Message-----
From: Jeffrey D. Brekke [] 
Sent: Wednesday, December 10, 2003 10:37 PM
To: Jakarta Commons Users List
Subject: Re: questions about FTP LIST processing (FTPFileListParser)

The list parsers are ( in my opinion ) on the road to deprecation in
favor of the entry parsers.  What I would like to do is implement the
deprecated list parsers with the entry parser implementations so we
don't have to support both any longer.  As soon as I get time.  Sorry
for the confusion.  I'd start with the entry parsers off the bat though.

>>>>> On Wed, 10 Dec 2003 15:24:57 -0700, Chris Malley 
>>>>> <> said:

> I did a little poking around in the source.  In case someone refers to

> this thread in the future...

> UnixFTPEntryParser is based on the DefaultFTPFileListParser 
> implementation, but they are not identical. UnixFTPEntryParser was 
> adapted to use regular expressions and to fit the new 
> FTPFileEntryParser interface, while DefaultFTPFileListParser uses the 
> old FTPFileListParser interface.

> And thanks again to Steve -- I never would have known to look at the 
> javadoc for UnixFTPEntryParser for info on what 
> DefaultFTPFileListParser does.

> -Chris

> Steve Cohen wrote:
>> Default is UnixFTPEntryParser.  I don't know what's different about 
>> EnterpriseUnixFTPEntryParser, someone contributed that.  The others 
>> are pretty straightforward, NT, OS2, VMS.  No doubt there are others.

>> If these don't fit your pattern, consider writing your own and 
>> contributing it.  It's pretty straightforward, you can use the others

>> as models, if you understand regular expressions. -----Original 
>> Message----- From: Chris Malley [] Sent: 
>> Wednesday, December 10, 2003 2:03 PM To: 
>> Subject: questions about FTP LIST 
>> processing (FTPFileListParser) I'm writing an FTP client that makes 
>> heavy use of the 'LIST' command, and I'm operating in an enviroment 
>> that has a wide range of FTP server types.  So the 'LIST' output is 
>> apt to vary.  The answers to these questions have eluded me so far: 
>> Which FTP servers does DefaultFTPFileListParser handle?  How do I 
>> decide when to use the various list parsers that are provided?  
>> (i.e., EnterpriseUnixFTPEntryParser, NTFTPEntryParser, 
>> OS2FTPEntryParser, UnixFTPEntryParser, VMSFTPEntryParser) Should I 
>> look at FTPClient.getSystemName()?...  Thanks, -Chris

> -- Chris Malley Contractor - PixelZoom, Inc.  Email @ EMC: 
> Voice @ EMC: (303)293-9331 x1235

> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Jeffrey D. Brekke                         
Wisconsin,  USA                           

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message