Re: Do we need a DCL debugger?
From: Bob Koehler (koehler_at_eisner.nospam.encompasserve.org)
Date: 09/08/03
- Next message: Wayne Sewell: "Re: The vultures are circulating"
- Previous message: Jeff Cameron: "Re: Limit Processor utilisation per user"
- In reply to: John Santos: "Re: Do we need a DCL debugger?"
- Next in thread: Dan O'Reilly: "Re: Do we need a DCL debugger?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 8 Sep 2003 07:31:52 -0500
In article <1030908013630.3498B-100000@Ives.egh.com>, John Santos <JOHN@egh.com> writes:
>
> Yeah fine, so what? Most graphical FTP interfaces attempt to display
> more than just the file names, and try to allow the user to sort and/or
> filter by names, dates, sizes, etc.
>
> NLST provides *ONLY* names. No other information. So it is inadequate
> for this purpose.
>
> LIST may have been only *MEANT* for display output, but when your
> only tool is a hammer, you pound in lots of screws.
So, instead of trying to defeat the RFC, wouldn't it be better to
add a new command to the RFC which provided the information you
want in a machine-parseable manner? Then everyone could program
to the RFC and not worry about what machine X version Y did with
vendor Z's stack.
IMHO this is long missing from the RFC, but it's hardly the only
thing missing from TCP/IP networking.
- Next message: Wayne Sewell: "Re: The vultures are circulating"
- Previous message: Jeff Cameron: "Re: Limit Processor utilisation per user"
- In reply to: John Santos: "Re: Do we need a DCL debugger?"
- Next in thread: Dan O'Reilly: "Re: Do we need a DCL debugger?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|