March 8th, 2003, 05:19 AM
March 8th, 2003, 06:45 AM
an ftp client is an ftp client they all follow the ftp protocol. In making an ftp client you dont have to make any of the functions you mentioned. all you have to do is pass the command to the server in the form of an ascii string.
in other words if you pass the string 'help' to the server you get a help listing from the server no matter what os the server is running on. Why...because thats the protocol.
as far as writing the server goes im not sure i understand what your saying. but linux is open source. just look at the scr of one of the ftp servers that have already been written to see whats required.
nothing has changed as far as a simple ftp client goes since it began 30 plus years ago and the gui type clients do nothing more than pass the same old ascii strings as their predessors did.
Bukhari:V3B48N826 “The Prophet said, ‘Isn’t the witness of a woman equal to half of that of a man?’ The women said, ‘Yes.’ He said, ‘This is because of the deficiency of a woman’s mind.’”
March 8th, 2003, 06:58 AM
Hey Hey Ajit...
something you might want to read if you are looking into making yourself an ftp client or server is reading the related RFC. This might give you a little more indepth look at how the file transfer protocol operates. You can find the RFC here
March 8th, 2003, 11:34 AM
FTP is a particularly annoying protocol, and I'd suggest you avoid it - it will complicate things significantly.
As you probably gather, if you've read the specs, FTP uses two sockets at once - one for control messages, the other for data. Worse still, the data connection is not always initiated by the client. Even worse still, the client sometimes sends its IP address to the server over the control connection.
All of these things make it highly error prone to program, and incompatible with many modern network (i.e. NAT) - you really don't want to code it if at all possible