🚀 go-pugleaf

"Hans Galema" <notused@notused.nl> wrote in message 
news:43790e73$1@newsgroups.borland.com...

> Do you use TClientSocket for the client part ?

That should not matter.  TServerSocket can accept, and communicate with, any 
client socket regardless of the environment it is coming from.  Everything 
ultmately operates on the same socket API anyway.  TCP, and thus socket 
behavior, is standardized across multiple platforms.

> Sorry. Servers do not connect to clients. A server can only
> listen and wait for connections.

In Bill's particular case, he is making his FTP client application open a 
separate listening server socket that the FTP server application will 
connect its own client socket to.  That is one scenerio in how the FTP 
protocol handles data connections.

> The OnRead event will never be triggered with stThreadBlocking.

That is correct only if Bill is not using the TServerSocket's OnGetThread 
event to provide his own cutom thread object for TServerSocket to use for 
each connection.  The default thread object that TServerSocket created by 
default does trigger the OnRead (and OnWrite) event.

> You have to actively read from a stream.

That is not always the case.

> Is DataSocket2 a TServerSocket ?

Given the example FTP commands that Bill showed, then his DataSocket would 
have to be a server socket, since that is what the PORT command requires.

> If yes why do you need 2 ?

He is only using 1 server socket.  He has to be sending his FTP commands 
over a client socket.

> We cannot check here the contents of Addr.

Presumably, Addr has been assigned to the IP that his TServerSocket is 
listening on.


Gambit