| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5167.1 | care to re-invent the wheel? | CUJO::SAMPSON | | Tue Jan 28 1997 22:41 | 4 |
| It can be done, and it has been done (probably more than once),
using $QIO calls, socket calls, and/or some combination. Unfortunately,
it seems that no implementation has so far been provided to the general
UCX user community.
|
| 5167.2 | | UCXAXP::GEMIGNANI | | Thu Jan 30 1997 18:18 | 3 |
|
There will not be such a beast in V4.2. It will almost definitely be
in by the UCX IP V6 release.
|
| 5167.3 | Commands for FTP (through socket) | CHEFS::DRSD11::THRUSSELL | Running on empty | Fri Feb 07 1997 05:30 | 15 |
| I only need a small sub-set of FTP functions so I could (in theory) write my
own interface using sockets.
I can connect to an FTP server (via a socket) and if I send it a message (any
data string) I get the following response back.
220 DRSD09 FTP Server (Version 3.2) Ready.
I cannot get any other response at all from the server.
Can anyone give me a clue on the required format of commands (e.g. for ls, get
and put) that I need to send through the socket to get some useful response from
the ftp server.
|
| 5167.4 | are you sure you want to do this? | UTRTSC::KNOPPERS | Oswald Knoppers | Fri Feb 07 1997 06:43 | 10 |
| Well, you can telnet to port 21 and type the 'help' command. This will
display a list of possible commands.
However I think it is not a trivial thing to implement a ftp client. Maybe
you can try using parts of public domain implementations of ftp, from Linux
for instance.
Regards,
Oswald
|
| 5167.5 | | UCXAXP::GEMIGNANI | | Tue Feb 11 1997 20:01 | 11 |
| There are two things here.
First of all, each FTP response is prefixed by a three digit response
code. 220 indicates that the server is ready for a new user.
Therefore, the client is expected to log a new user in. This is all
outlined in RFC-959.
Something important that Oswald stumbled onto without it becoming
obvious, is that the FTP server and client speak the TELNET protocol.
Each command (and response) is terminated by a <CR><LF>, which is the
NVT (network virtual terminal) equivalent of \n (newline).
|