RFC 949 (rfc949) - Page 2 of 2

FTP unique-named store command

RFC 949                                                        July 1985
FTP Unique-Named Store Command


   much like work, though--even if it does have the subtle virtue of
   finally getting control arguments into FTP.  Therefore, why not just
   include it in a suitable response-code's free text field (unless, of
   course, an avalanche of comments comes in urging it not be done at
   all)?

   Note, by the way, that the intent here is emphatically not to
   sidestep whatever access control, authentication, and accounting
   mechanisms Hosts might have in play before the user can do an old
   STOR or a new STOU, but with suitable publicized ID's and passwords
   it could be almost as good as the proposal made in RFC 505.

RECOMMENDATION

   Add a new command, STOU, to FTP, which behaves like STOR except that
   the resultant file is to be created in the current directory under a
   name unique to that directory.   The 250 Transfer Started response
   should include the name generated (unless the copy of FTP I have is
   so old that 250 isn't the right number any more).






























Padlipsky