rtriw44
3.77 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
<?xml version="1.0" encoding="iso-8859-1"?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Real-Time Resources in the Web</title>
<meta name="GENERATOR" content="amaya V4.1" />
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
</head>
<body>
<p><a href="../../">W3C</a> Addressing</p>
<h1>Real-Time Resources in the Web: IRC, Telephone, Instant Messaging</h1>
<address>
DRAFT started 7 Jan 2001 by <a href="/People/Connolly/">Dan Connolly</a><br
/>
<small>$Revision: 1.8 $ of $Date: 2001/01/15 03:17:34 $ by $Author: connolly
$</small>
</address>
<p>See:</p>
<ul>
<li><a href="http://dev.w3.org/cvsweb/2001/telagent/">telagent</a> Jan 2001
<p>an HTTP agent to help you place and receive phone calls.</p>
</li>
</ul>
<p></p>
<p>cf Engelbart's argument for <a
href="http://www.bootstrap.org/augdocs/augment-132082.htm#12B">Shared-Window
Teleconferencing</a>.</p>
<p>Example:</p>
<blockquote>
<p>Once you have the client installed, you need to tell it to connect to our
server, which is called <code>irc.debian.org</code>. In most clients, you
can do that by typing:</p>
<pre>/server irc.debian.org</pre>
<p>Once you are connected, join channel <code>#debian</code> by typing</p>
<pre>/join #debian</pre>
<p>Note: X-Chat, Zircon and other GUI-based clients are different.</p>
<address>
<p>-- <a href="http://www.debian.org/support#irc">IRC section</a> of <a
href="http://www.debian.org/support">Debian Support</a> <br />
Last Modified: Fri, Nov 17 15:24:07 UTC 2000</p>
</address>
</blockquote>
<p>But...</p>
<blockquote>
<p>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.</p>
<address>
<p>-- <a href="/Addressing/">Addressing</a></p>
</address>
</blockquote>
<p>@@compare with some old "log into this FTP server..." directions</p>
<p>mIRC does (nearly) The Right Thing. cf timbl's <a
href="mid:013201c04e62$a282da60$e8001d12@CREST">message</a> of Tue, 14 Nov
2000 12:45:09 -0500</p>
<p>relevant schemes: <a href="/Addressing/schemes.html#irc">irc</a>: <a
href="/Addressing/schemes.html#tel">tel</a>: callto: (misnomer, ala <a
href="/Addressing/schemes.html#mailto">mailto</a>:); contrast with tv: ,which
is broadcast (lots of readers but just one writer.)</p>
<p>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
<em>sending</em> 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.</p>
<p><a href="http://www.gnu.org/software/gnucomm/gnucomm.html">GNUCOMM</a>
looks interesting 2Jan2001</p>
<h2>See also:</h2>
<ul>
<li>Rohit's internet scale notification workshop</li>
<li>SIP</li>
<li>the mess in IETF IM WGs (cf fork)</li>
<li>mozilla bug <a
href="http://bugzilla.mozilla.org/show_bug.cgi?id=2110">bug 2110</a> about
syntactic support for irc: URIs.</li>
</ul>
</body>
</html>