From WikiChip
Difference between revisions of "mirc/dcc protocols"
< mirc

(Created page with "This is a holding page for documenting how DCC CHAT and SEND protocols work in detail. It will be an expanded version of https://www.mirc.com/help/html/index.html?dcc_resume_p...")
 
 
Line 1: Line 1:
 +
{{mirc title|DCC protocols}}
 
This is a holding page for documenting how DCC CHAT and SEND protocols work in detail. It will be an expanded version of https://www.mirc.com/help/html/index.html?dcc_resume_protocol.html to include information relating to mIRC from https://en.wikipedia.org/wiki/Direct_Client-to-Client.
 
This is a holding page for documenting how DCC CHAT and SEND protocols work in detail. It will be an expanded version of https://www.mirc.com/help/html/index.html?dcc_resume_protocol.html to include information relating to mIRC from https://en.wikipedia.org/wiki/Direct_Client-to-Client.
  

Latest revision as of 17:40, 1 October 2018

This is a holding page for documenting how DCC CHAT and SEND protocols work in detail. It will be an expanded version of https://www.mirc.com/help/html/index.html?dcc_resume_protocol.html to include information relating to mIRC from https://en.wikipedia.org/wiki/Direct_Client-to-Client.

The reason this is needed is because the protocols vary depending on:

  • DCC Passive on / off
  • DCC Resume on / off
  • Use of quoted filenames / filenames with spaces in them

If you are processing the CTCP messages used to control DCC in your scripts, then you will need to code for these variances.