1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding] send_cmd in non-protocol modules
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20send_cmd%20in%20non-protocol%20modules&In-Reply-To=200505091158250255.C8AD859E%40smtp.messaging.ca.mci.com">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"003123.html">
11 <LINK REL=
"Next" HREF=
"003125.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding] send_cmd in non-protocol modules
</H1>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20send_cmd%20in%20non-protocol%20modules&In-Reply-To=200505091158250255.C8AD859E%40smtp.messaging.ca.mci.com"
17 TITLE=
"[IRCServices Coding] send_cmd in non-protocol modules">achurch at achurch.org
19 <I>Tue May
10 12:
52:
47 PDT
2005</I>
21 <LI>Previous message:
<A HREF=
"003123.html">[IRCServices Coding] send_cmd in non-protocol modules
23 <LI>Next message:
<A HREF=
"003125.html">[IRCServices Coding] send_cmd in non-protocol modules
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#3124">[ date ]
</a>
27 <a href=
"thread.html#3124">[ thread ]
</a>
28 <a href=
"subject.html#3124">[ subject ]
</a>
29 <a href=
"author.html#3124">[ author ]
</a>
34 <PRE> That would certainly be preferable, but so far nobody seems to have
35 done that (nor do the ircd developers seem very interested in working
36 together on creating such a document).
38 Actually, that's not quite accurate, since RFCs
2810-
2813 were
39 published at one point, but nobody seems to be paying attention to them...
42 <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>
43 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
45 ><i> Would it not therefore seem more logical to update or create new RFCs pertaining to IRC, instead of having to customize Services each time another non-RFC-compliant IRCd implements a 'desireable' feature? I'm no software developer, but if I were, I wouldn't consider it unreasonable to set out some guidelines within whose confines I'd prefer to remain.
46 </I>><i> That being said, if IRCServices continues to implement a number of ad-hoc modifications which don't follow an RFC, what happens if/when a new RFC *is* written which serves to address the aforementioned ad-hoc changes? More work for the developers, from what I can tell, to ensure their previously implemented workarounds meet the newly released standards.
51 </I>><i>On
07/
05/
2005 at
11:
01 PM Craig Edwards wrote:
53 </I>>><i>IRC is changing. It has been changing since day one, the software which
54 </I>>><i>is used for IRC must change with it. IRCServices is being left behind by
55 </I>>><i>other software which *does* tolerate changes to the spec, and it saddens
56 </I>>><i>me to see software i love becoming deprecated because of it :-(
58 </I>>><i>I'm sure there are many IRCu users out there who would disagree with
59 </I>>><i>your opinion, and as it stands ircservices simply cannot support them,
60 </I>>><i>even though it is one of the most popular IRCds. I'd say this ircd has
61 </I>>><i>more problems than mine as mine is tolerant to 'assumptions' and will
62 </I>>><i>rewrite the RFC commands to something it understands -- IRCu (P10) will
63 </I>>><i>not ;-)
67 </I>>><i>Andrew Church wrote:
68 </I>>>>><i>IRCServices
5 has protocol modules which allow it to connect to many
69 </I>>>>><i>different kinds of ircds easily. Great idea. However, the core blatantly
70 </I>>>>><i>uses send_cmd, and makes assumptions about the format of specific
71 </I>>>>><i>commands,
74 </I>>>><i> This is by design. The only reason for protocol modules in the
76 </I>>>><i> place is to kludge around variations in what ought to be a standard. If
77 </I>>>><i> you have an ircd that's so bizarre it can't even understand a NOTICE
78 </I>>>><i> message, then Services won't support it. Sorry, but I don't have the
80 </I>>>><i> or interest to deal with such software.
82 </I>>>><i> --Andrew Church
83 </I>>>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>
84 </I>>>><i> <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
85 </I>>>><i> ------------------------------------------------------------------
86 </I>>>><i> To unsubscribe or change your subscription options, visit:
87 </I>>>><i> <A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
92 </I>>><i>WinBot IRC client developer:
<A HREF=
"http://www.winbot.co.uk">http://www.winbot.co.uk
</A>
93 </I>>><i>ChatSpike - The users network:
<A HREF=
"http://www.chatspike.net">http://www.chatspike.net
</A>
94 </I>>><i>InspIRCd - Modular IRC server:
<A HREF=
"http://www.inspircd.org">http://www.inspircd.org
</A>
95 </I>>><i>Online RPG Developer:
<A HREF=
"http://www.ssod.org">http://www.ssod.org
</A>
97 </I>>><i>------------------------------------------------------------------
98 </I>>><i>To unsubscribe or change your subscription options, visit:
99 </I>>><i><A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
103 </I>><i>------------------------------------------------------------------
104 </I>><i>To unsubscribe or change your subscription options, visit:
105 </I>><i><A HREF=
"http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
113 <LI>Previous message:
<A HREF=
"003123.html">[IRCServices Coding] send_cmd in non-protocol modules
115 <LI>Next message:
<A HREF=
"003125.html">[IRCServices Coding] send_cmd in non-protocol modules
117 <LI> <B>Messages sorted by:
</B>
118 <a href=
"date.html#3124">[ date ]
</a>
119 <a href=
"thread.html#3124">[ thread ]
</a>
120 <a href=
"subject.html#3124">[ subject ]
</a>
121 <a href=
"author.html#3124">[ author ]
</a>
projects / irc.git / blob