🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> "qyte" <gyte@vivodinet.gr> wrote in message
> news:4228f8c1$1@newsgroups.borland.com...
> 
> 
>>Does anyone know what exactly should i call lock
>>and unlock functions for?
> 
> 
> Nothing.  They are called automatically by the TCustomWinSocket internally.
> 
> 
>>will they work on non-blocking mode?
> 
> 
> Yes.
> 
> 
>>if there are 4 Sockets using the same port
> 
> 
> Using in what way?  Bound to locally, or connecting to remotely?
> 
> 
>>and i use Lock on the first will the others be able to use the Port for
> 
> reading and writing?
> 
> Lock() and Unlock() only affect the socket they are called on.  They are
> used to provide thread-safe access to the socket so that multiple threads do
> not try to all read from, or all write to, the socket at the same time.
> 
> 
> Gambit
> 

Let's say that i have four TClientSockets And 1 TServerSocket; During 
their OnConnect events i have declared the following:
TCustomWinSocket *sock[4];

In The Server sock[ActiveConnections-1]=Socket;

and in each client i assosciate them like sock[0]=Socket...
Because I Know the order in which they connect.

how can i be certain that when i call sock[0]->SendBuf No other can 
read(mainly) or write at the same time. It is abvious that they are all 
using the same port. Is Their any way of Doing Such A Thing? The Sockets 
Are connected as follows.

Server----Client
sock[0]<->sock[0]
sock[1]<->sock[2]
sock[2]<->sock[1]
sock[3]<->sock[3]

even though sock[1] sends only and sock[2] receives only sometimes their 
is confusion when sock[1]->sendbuf is called from both the server and 
the client and they stuck. i made that way believing that they would be 
independent but even now they aren't. Do you know what i can do>