Steve, We came across the problem with OpenVMS's listings. Monday I'll get a sample listing with an entry that spans two lines and add it to the VMSFTPEntryParserTest.
Our idea was to let the regular expression handle parsing the entries and not rely on the line endings. I believe this is similar to how the current parsing works. The problem is you need to either pass around the entire list unparsed, and parse it when needed, or parse the entire list up front, creating all the FTPFile entries right away. I believe you wrote the new parsers to avoid this up front object creation and parsing assuming one entry per line. "Steve Cohen" <[EMAIL PROTECTED]> writes: > No, I haven't solved that one. It's been around for a while. The > line-based parsing has been standard in this package since it began. > > I think we could, in principle, solve it by making each parser > define a method that returns the entry delimiter. Instead of > calling readLine() we would have it read from the stream until the > delimiter was found. That delineates an entry. > > Do we have the specs on which systems have multi-line entries and > what the entry delimiter on these systems is? I'd like to have a > feel for what the extent of the variety is in the real world before > coding an interface. > > In fact, it would probably be a very good idea to put together a > list all the ftp systems this project knows it wants to support and > their parameters before getting too deep into coding. > > > -----Original Message----- > From: Jeffrey D. Brekke [mailto:[EMAIL PROTECTED] > Sent: Fri 2/28/2003 9:54 PM > To: Steve Cohen > Cc: > Subject: Re: FW: Problems using maven site:deploy > > Sounds great, you can answer the next question on the commons-dev > list maybe. Did you find any solutions for ftp entries that span > more than one line? -- ===================================================================== Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
