Jump to content

Talk:Direct Client-to-Client

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by ÜberRegenbogen (talk | contribs) at 14:03, 21 July 2006. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

DCC2 is in the works (Slashdot Article on DCC2). While this might fall under the "extensions" of DCC, it looks like it's going to be a complete replacement. Perhaps it should be mentioned in the article? -- Kowh 01:53, 26 Apr 2004 (UTC)

I'm adding a note to the effect that DCC FSERVE is only available under mIRC. It doesn't exist in X-Chat or anywhere in the ircII family. --Cuervo 01:36, 9 Apr 2005 (UTC)

Correct me if I'm wrong, but I don't think FSERV is a separate service at the DCC level, but rather uses CHAT (or in place of that, CTCP) and SEND/XMIT together to create something else. This kind of scripting is not exclusive to mIRC either. I've updated the article to reflect this. --Andyluciano 22 Aug 2005, 05:33 (UTC)
That is correct. FSERV uses a DCC CHAT based interface for the user to find and request files, which are then send via a normal DCC SEND. And, yes, it has been implemented under other clients (in some cases as scripts, and in some (as with mIRC) as a built-in feature).
As for DCC2: it has been in the works for several years, and shows little sign of going anywhere. At the core, it is a good idea to completely scrap DCC—which is an atrocious, poorly (and barely) planned mess. I don't remember its particulars, but it would be better to replace it with a far more robust architecture, with a minimum (perhaps utilising scp or other existing secure tunneled protocol) rather than just a new handshaking method. (But i digress, and this is not the place.) —StationaryTraveller 14:03, 21 July 2006 (UTC)[reply]

CTCP vs. CTCP reply

Since the reply to a PRIVMSG should not be another PRIVMSG, a CTCP reply is implemented with a NOTICE. But is the DCC ACCEPT reply, which is a reply to a reply, a CTCP message or a CTCP reply? I guess that it should be a reply, and implemented with NOTICE, but it would be nice to have this confirmed.

XMIT

The only specification I could find for XMIT was an old working draft, which expired long ago. Was XMIT never accepted as a standard?

Programming libaries

Shouldnt we include something about programming libraries avaliable to code such DCC stuffs??