]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/1999/000185.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 1999 / 000185.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] New IRC protocol revised
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20IRC%20protocol%20revised&In-Reply-To=">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="000183.html">
11 <LINK REL="Next" HREF="000186.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] New IRC protocol revised</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20IRC%20protocol%20revised&In-Reply-To="
17 TITLE="[IRCServices] New IRC protocol revised">achurch at dragonfire.net
18 </A><BR>
19 <I>Thu Oct 7 21:59:45 PDT 1999</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000183.html">[IRCServices] New IRC protocol revised
22 </A></li>
23 <LI>Next message: <A HREF="000186.html">[IRCServices] what do they think ?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#185">[ date ]</a>
27 <a href="thread.html#185">[ thread ]</a>
28 <a href="subject.html#185">[ subject ]</a>
29 <a href="author.html#185">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i>If I read this correctly this new protocol will allow more than one
35 </I>&gt;<i>connection to the same server at the same time?
36 </I>
37 Yes.
38
39 &gt;<i>... if so how will Jupes be handled? ...
40 </I>
41 You won't be able to do them the way you do now; you'd need to
42 modify servers' configurations and/or add a new command to keep a server
43 out.
44
45 Come to think of it, this does raise an interesting problem where a
46 server connects with the same name and ID as another server already on
47 the network, causing some/all messages to that server to be misdirected.
48 Maybe we need a remote address check on duplicate connections (which
49 would allow jupes to work again).
50
51 &gt;<i>and how will the network know which way to send data, so that
52 </I>&gt;<i>the server that is connected more than once don't receive it's data from
53 </I>&gt;<i>more than one source?
54 </I>
55 This is described in section 1.6.
56
57 &gt;<i>With DSL growing so popular the end user portion is already gorwing &quot;more
58 </I>&gt;<i>stable&quot;. :)
59 </I>
60 Tell that to one of my friends on EsperNet who delinked his server
61 because his DSL connection was so unstable.
62
63 Also remember that stability is not just the end-user-to-uplink
64 connection, but all the routers on the paths between the servers/clients--
65 it's actually the latter part that worries me the most.
66
67 --Andrew Church
68 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at dragonfire.net</A>
69 <A HREF="http://achurch.dragonfire.net/">http://achurch.dragonfire.net/</A>
70 ---------------------------------------------------------------
71 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
72 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
73
74 </PRE>
75
76 <!--endarticle-->
77 <HR>
78 <P><UL>
79 <!--threads-->
80 <LI>Previous message: <A HREF="000183.html">[IRCServices] New IRC protocol revised
81 </A></li>
82 <LI>Next message: <A HREF="000186.html">[IRCServices] what do they think ?
83 </A></li>
84 <LI> <B>Messages sorted by:</B>
85 <a href="date.html#185">[ date ]</a>
86 <a href="thread.html#185">[ thread ]</a>
87 <a href="subject.html#185">[ subject ]</a>
88 <a href="author.html#185">[ author ]</a>
89 </LI>
90 </UL>
91
92 </body></html>