"Danila Vershinin" <profyprepATyandexDOTru> wrote in message
news:447b6411$1@newsgroups.borland.com...
> In particular I am interested in UserMode (amAway, amInvisible, amWallops,
> amRestricted, amOperator, amLocalOperator, amReceiveServerNotices)
> options set.
That should be self-explanatory for you. Those are flags for the different
user modes that are available in the IRC protocol.
> Also ReuseSocket, seems new property to me.
ReuseSocket only applies when you use the BoundIP/BoundPort properties, such
as when you have multiple ethernet cards installed, or a firewall. When a
socket is closed, the OS internally keeps the socket open for a period of
time to make sure that all data from that socket is received. During that
time, under normal situations a new socket cannot be bound to the same local
IP/Port that an existing socket is still using. The ReuseSocket property
allows the new socket to use the same IP/Port. The reason you can ignore
the ReuseSocket property when ot using the BoundIP/BoundPort properties is
because new sockets will bind to random IP/Port values to ensure their
uniqueness.
> And ReadTimeout...
That should be self-explanatory as well. It is the reading timeout for the
socket. If a read operation takes too long, an exception will be thrown.
ReadTimeout is not a new property in Indy, it has always been available.
Gambit
