🚀 go-pugleaf

Well basically i use the Caps Lock istead of the shift key..:)).By the way
ftp and trivial ftp are diffrent things
FTP:FTP is commonly run on two ports, 20 and 21. Port 20 is a data stream
which transfers the data between the client and the server. Port 21 is the
control stream and is the port where commands are passed to the ftp
server.FTP is an 8-bit client-server protocol,
TRIVIAL FTP:Trivial File Transfer Protocol (TFTP) is a very simple file
transfer protocol akin to a basic version of FTP
  a.. Uses UDP (port 69) as its transport protocol (unlike FTP which uses
TCP port 21).
  b.. It cannot list directory contents
  c.. No authentication or encryption mechanisms
  d.. Used to read files from/write files to a remote server
  e.. Supports three different transfer modes, "netascii", "octet" and
"mail", with the first two corresponding to the "ascii" and "image" (binary)
modes of the FTP protocol.
from http://en.wikipedia.org/

so ftp and trivial ftp arent exactly the same protocols, are they?
? "Hans Galema" <notused@notused.nl> ?????? ??? ??????
news:422e02e9@newsgroups.borland.com...
> lakis wrote:
> > ... now one
> > final question and really sorry for the trouble of continuous
> > questions..
>
> You can ask as many questions as you want. That is no trouble at all.
> You only way you cause trouble is by not writing in a normal way
> with a kapital letter at the start of a sentence. Is your shift key
> blocked ?
>
>  > if i use indy trivial ftp components for file transfer means i
> > am using trivial ftp protocol,if i use indy ftp components for file
transfer
> > means i am using ftp protocol etc.
>
> No both use the same ftp protocol. They could also connect to the
> same server because the server speaks ftp.
>
> > when i send
> > file through sockets in this way what protocol am i using?(or im not
using
> > any protocol at all?)
>
> You use a protocol. But it has no name. A protocol is the way a client
> and a server exchange messages. If the server send you a bunch of data
> then it can for instance send four bytes (an int) first with the size
> of the message. A client has to read that size first. As simple as it
> is: this is a protocol. You have to know that the size comes first and
> act accordingly.
>
> Hans.