Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Ed. note: Most people should probably skip this file and instead see the CTCP
specification which updates and includes this file in its entirety and talks
about other related stuff. I kept this file mostly for historical reasons only.
-Jolo
Why DCC?
========
How?
====
Implementation
==============
Initiator:
DCC command issued.
Create a socket, bind it to INADDR_ANY, port 0, and
make it passive (a listening socket).
Send the recipient a DCC request via CTCP supplying
the address and port of the socket. (This
is ideally taken from the address of the local
side of the socket which is connected to a
server. This is presumably the interface on
the host which is closest to the rest of
the net, and results in one less routing hop
in the case of gateway nodes).
Continue normally until a connection is received.
On a connection:
Accept the connection.
Close the original passive socket.
Conduct transaction on the new socket.
Acceptor:
CTCP DCC request received.
Record information on the DCC request and notify the user.
--
_______________________________________________________________________________
troy@cbme.unsw.EDU.AU Overworked, overcommited and always multitasking.
Opinions expressed are not those of the CBME or UNSW, but are my opinions only.
You are free to adopt them. I suggest you adopt them. You will adopt them!
-navigational bar-
[ go back | search | help | send email ]