W3C Addressing

Real-Time Resources in the Web: IRC, Telephone, Instant Messaging

DRAFT started 7 Jan 2001 by Dan Connolly
$Revision: 1.8 $ of $Date: 2001/01/15 03:17:34 $ by $Author: connolly $

See:

cf Engelbart's argument for Shared-Window Teleconferencing.

Example:

Once you have the client installed, you need to tell it to connect to our server, which is called irc.debian.org. In most clients, you can do that by typing:

/server irc.debian.org

Once you are connected, join channel #debian by typing

/join #debian

Note: X-Chat, Zircon and other GUI-based clients are different.

-- IRC section of Debian Support
Last Modified: Fri, Nov 17 15:24:07 UTC 2000

But...

Uniform Resource Identifiers (URIs, aka URLs) are short strings that identify resources in the web: documents, images, downloadable files, services, electronic mailboxes, and other resources. They make resources available under a variety of naming schemes and access methods such as HTTP, FTP, and Internet mail addressable in the same simple way. They reduce the tedium of "log in to this server, then issue this magic command ..." down to a single click.

-- Addressing

@@compare with some old "log into this FTP server..." directions

mIRC does (nearly) The Right Thing. cf timbl's message of Tue, 14 Nov 2000 12:45:09 -0500

relevant schemes: irc: tel: callto: (misnomer, ala mailto:); contrast with tv: ,which is broadcast (lots of readers but just one writer.)

hmm... how would I do this, say, in xchat? I'd like to use XML/HTTP for peer-to-peer communication on the desktop (contrast with CORBA approach... isomorphism, based on XML Schemas? hmm...). So xchat should listen for requests; hm... in this case, is it a GET request? If so, that would simplify things: just have the client presenting the document with the link proxy out to the xchat server, and away we go. But... is joining a channel something you can/should be held accountable for? (@@cf HTTP section about safe methods) if it is, this isn not a GET, but some sort of POST. Hm... surely sending something to a channel is a POST; but perhaps joining is not? hmm... joining is like Rohit's SUBSCRIBE; in that sense, it's not safe.

GNUCOMM looks interesting 2Jan2001

See also: