imported>Kunda m (quick page) |
imported>mutante mNo edit summary |
||
Line 1:
Direct Client Connection<br>
DCC uses direct [[TCP]] connections between the clients
See: [[IRC]]▼
taking part to carry data. There is no flood control, so
packets can be sent at full speed, and there is no
dependance on server links (or load imposed on them). In
addition, since only the initial handshake for DCC conections
is passed through the [[IRC]] [[network]], it is impossible for
Operators with cracked servers to spy on DCC messages.
The initial [[socket]] for a DCC connection is created
by the side that initiates (Offers) the connection. This socket
should be a [[TCP]] socket bound to INADDR_ANY, listening for
connections.
The following DCC connection types are known to [[IRCII]]:
Type Purpose Argument
CHAT To carry a secure conversation the string "chat"
SEND To send a file to the recipient the file name
* [http://www.irchelp.org/irchelp/rfc/dccspec.html A description of the DCC protocol]
▲Also See: [[IRC]]
[[Category:Protocols]]
[[Category:IRC]]
|
Revision as of 19:20, 2 March 2005
Direct Client Connection
DCC uses direct TCP connections between the clients taking part to carry data. There is no flood control, so packets can be sent at full speed, and there is no dependance on server links (or load imposed on them). In addition, since only the initial handshake for DCC conections is passed through the IRC network, it is impossible for Operators with cracked servers to spy on DCC messages.
The initial socket for a DCC connection is created by the side that initiates (Offers) the connection. This socket should be a TCP socket bound to INADDR_ANY, listening for connections.
The following DCC connection types are known to IRCII:
Type Purpose Argument CHAT To carry a secure conversation the string "chat" SEND To send a file to the recipient the file name
Also See: IRC