×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Jeff,
It is implied that the FTP server type (IBM
i, Windows, Linux, etc) has a bearing on what is acceptable. I would like
to use a way that works no matter what the server side is. Antyone know?
The server will make a difference because there is no standard command in
the RFC for comments.
However, there is a standard command all servers should support called
NOOP. As implied, it performs no operation. What is it intended to be
used for is as a "keep alive" command so that sockets won't time out. When
sent to a server, it is just supposed to accept it and send back an OK
response.
I don't know that all servers will ignore text beyond the NOOP, but the
ones I just tried did. So you MAY be able to get by with using NOOP and a
space as the prefix to your comments. The actual RFC 959 text for the
command is:
NOOP (NOOP)
This command does not affect any parameters or previously
entered commands. It specifies no action other than that the
server send an OK reply.
I interpret that to mean you should be able to send parameters (your
comments) and have them ignored. And that is how the servers I tried
acted. But I don't know there is any guarantee all servers will act that
way.
Back in the days of early BASIC, where comments began with REM, a friend of
mine always began his programs with
10 REMARKABLE program that ...
because you didn't even need a space after the REM. But put at least one
space after your NOOP.
Doug
midrange.com
