projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] send_cmd in non-protocol modules | |
| 5 | </TITLE> | |
| 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=42803119.47206%40msgid.achurch.org"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="003124.html"> | |
| 11 | <LINK REL="Next" HREF="003126.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] send_cmd in non-protocol modules</H1> | |
| 15 | <B>Craig Edwards</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20send_cmd%20in%20non-protocol%20modules&In-Reply-To=42803119.47206%40msgid.achurch.org" | |
| 17 | TITLE="[IRCServices Coding] send_cmd in non-protocol modules">brain at winbot.co.uk | |
| 18 | </A><BR> | |
| 19 | <I>Tue May 10 05:03:35 PDT 2005</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="003124.html">[IRCServices Coding] send_cmd in non-protocol modules | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="003126.html">[IRCServices Coding] a little feature suggestion | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#3125">[ date ]</a> | |
| 27 | <a href="thread.html#3125">[ thread ]</a> | |
| 28 | <a href="subject.html#3125">[ subject ]</a> | |
| 29 | <a href="author.html#3125">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>nobody pays any attention to them because a lot of it was unfortunately | |
| 35 | IRCNet specific. What makes it worse is that now IRCNet is throwing | |
| 36 | their own specs in the bin (without writing new ones i might add to take | |
| 37 | their place) -- for example did you know the pipe character ("|") is now | |
| 38 | ILLEGAL in nicknames on ircnet? - it's a new feature of their ircd2.x | |
| 39 | line. They took it *out* of the BNF for allowed nicknames, i'm not just | |
| 40 | referring to a Q line! Not just this but there have been many other | |
| 41 | changes 'in the name of compatibility'. Compatibility? pffft. | |
| 42 | ||
| 43 | Brain | |
| 44 | ||
| 45 | Andrew Church wrote: | |
| 46 | ><i> That would certainly be preferable, but so far nobody seems to have | |
| 47 | </I>><i> done that (nor do the ircd developers seem very interested in working | |
| 48 | </I>><i> together on creating such a document). | |
| 49 | </I>><i> | |
| 50 | </I>><i> Actually, that's not quite accurate, since RFCs 2810-2813 were | |
| 51 | </I>><i> published at one point, but nobody seems to be paying attention to them... | |
| 52 | </I>><i> | |
| 53 | </I>><i> --Andrew Church | |
| 54 | </I>><i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A> | |
| 55 | </I>><i> <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 56 | </I>><i> | |
| 57 | </I>><i> | |
| 58 | </I>>><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. | |
| 59 | </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. | |
| 60 | </I>>><i> | |
| 61 | </I>>><i>David | |
| 62 | </I>>><i> | |
| 63 | </I>>><i> | |
| 64 | </I>>><i>On 07/05/2005 at 11:01 PM Craig Edwards wrote: | |
| 65 | </I>>><i> | |
| 66 | </I>>><i> | |
| 67 | </I>>>><i>IRC is changing. It has been changing since day one, the software which | |
| 68 | </I>>>><i>is used for IRC must change with it. IRCServices is being left behind by | |
| 69 | </I>>>><i>other software which *does* tolerate changes to the spec, and it saddens | |
| 70 | </I>>>><i>me to see software i love becoming deprecated because of it :-( | |
| 71 | </I>>>><i> | |
| 72 | </I>>>><i>I'm sure there are many IRCu users out there who would disagree with | |
| 73 | </I>>>><i>your opinion, and as it stands ircservices simply cannot support them, | |
| 74 | </I>>>><i>even though it is one of the most popular IRCds. I'd say this ircd has | |
| 75 | </I>>>><i>more problems than mine as mine is tolerant to 'assumptions' and will | |
| 76 | </I>>>><i>rewrite the RFC commands to something it understands -- IRCu (P10) will | |
| 77 | </I>>>><i>not ;-) | |
| 78 | </I>>>><i> | |
| 79 | </I>>>><i>Brain | |
| 80 | </I>>>><i> | |
| 81 | </I>>>><i>Andrew Church wrote: | |
| 82 | </I>>>><i> | |
| 83 | </I>>>>>><i>IRCServices 5 has protocol modules which allow it to connect to many | |
| 84 | </I>>>>>><i>different kinds of ircds easily. Great idea. However, the core blatantly | |
| 85 | </I>>>>>><i>uses send_cmd, and makes assumptions about the format of specific | |
| 86 | </I>>>>>><i>commands, | |
| 87 | </I>>>>><i> | |
| 88 | </I>>>>><i> | |
| 89 | </I>>>>><i> This is by design. The only reason for protocol modules in the | |
| 90 | </I>>>><i> | |
| 91 | </I>>>><i>first | |
| 92 | </I>>>><i> | |
| 93 | </I>>>>><i>place is to kludge around variations in what ought to be a standard. If | |
| 94 | </I>>>>><i>you have an ircd that's so bizarre it can't even understand a NOTICE | |
| 95 | </I>>>>><i>message, then Services won't support it. Sorry, but I don't have the | |
| 96 | </I>>>><i> | |
| 97 | </I>>>><i>time | |
| 98 | </I>>>><i> | |
| 99 | </I>>>>><i>or interest to deal with such software. | |
| 100 | </I>>>>><i> | |
| 101 | </I>>>>><i> --Andrew Church | |
| 102 | </I>>>>><i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A> | |
| 103 | </I>>>>><i> <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 104 | </I>>>>><i>------------------------------------------------------------------ | |
| 105 | </I>>>>><i>To unsubscribe or change your subscription options, visit: | |
| 106 | </I>>>>><i><A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
| 107 | </I>>>>><i> | |
| 108 | </I>>>>><i> | |
| 109 | </I>>>><i> | |
| 110 | </I>>>><i>-- | |
| 111 | </I>>>><i>WinBot IRC client developer: <A HREF="http://www.winbot.co.uk">http://www.winbot.co.uk</A> | |
| 112 | </I>>>><i>ChatSpike - The users network: <A HREF="http://www.chatspike.net">http://www.chatspike.net</A> | |
| 113 | </I>>>><i>InspIRCd - Modular IRC server: <A HREF="http://www.inspircd.org">http://www.inspircd.org</A> | |
| 114 | </I>>>><i>Online RPG Developer: <A HREF="http://www.ssod.org">http://www.ssod.org</A> | |
| 115 | </I>>>><i>-- | |
| 116 | </I>>>><i>------------------------------------------------------------------ | |
| 117 | </I>>>><i>To unsubscribe or change your subscription options, visit: | |
| 118 | </I>>>><i><A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
| 119 | </I>>><i> | |
| 120 | </I>>><i> | |
| 121 | </I>>><i> | |
| 122 | </I>>><i>------------------------------------------------------------------ | |
| 123 | </I>>><i>To unsubscribe or change your subscription options, visit: | |
| 124 | </I>>><i><A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
| 125 | </I>><i> | |
| 126 | </I>><i> ------------------------------------------------------------------ | |
| 127 | </I>><i> To unsubscribe or change your subscription options, visit: | |
| 128 | </I>><i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
| 129 | </I>><i> | |
| 130 | </I>><i> | |
| 131 | </I> | |
| 132 | -- | |
| 133 | WinBot IRC client developer: <A HREF="http://www.winbot.co.uk">http://www.winbot.co.uk</A> | |
| 134 | ChatSpike - The users network: <A HREF="http://www.chatspike.net">http://www.chatspike.net</A> | |
| 135 | InspIRCd - Modular IRC server: <A HREF="http://www.inspircd.org">http://www.inspircd.org</A> | |
| 136 | Online RPG Developer: <A HREF="http://www.ssod.org">http://www.ssod.org</A> | |
| 137 | -- | |
| 138 | </PRE> | |
| 139 | ||
| 140 | ||
| 141 | <!--endarticle--> | |
| 142 | <HR> | |
| 143 | <P><UL> | |
| 144 | <!--threads--> | |
| 145 | <LI>Previous message: <A HREF="003124.html">[IRCServices Coding] send_cmd in non-protocol modules | |
| 146 | </A></li> | |
| 147 | <LI>Next message: <A HREF="003126.html">[IRCServices Coding] a little feature suggestion | |
| 148 | </A></li> | |
| 149 | <LI> <B>Messages sorted by:</B> | |
| 150 | <a href="date.html#3125">[ date ]</a> | |
| 151 | <a href="thread.html#3125">[ thread ]</a> | |
| 152 | <a href="subject.html#3125">[ subject ]</a> | |
| 153 | <a href="author.html#3125">[ author ]</a> | |
| 154 | </LI> | |
| 155 | </UL> | |
| 156 | ||
| 157 | </body></html> |