software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2005/003120.html

   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=427D2D50.8070400%40winbot.co.uk">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="003119.html">
  11    <LINK REL="Next"  HREF="003121.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] send_cmd in non-protocol modules</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20send_cmd%20in%20non-protocol%20modules&In-Reply-To=427D2D50.8070400%40winbot.co.uk"
  17        TITLE="[IRCServices Coding] send_cmd in non-protocol modules">achurch at achurch.org
  18        </A><BR>
  19     <I>Sun May  8 06:47:32 PDT 2005</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003119.html">[IRCServices Coding] send_cmd in non-protocol modules
  22 </A></li>
  23         <LI>Next message: <A HREF="003121.html">[IRCServices Coding] send_cmd in non-protocol modules
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3120">[ date ]</a>
  27               <a href="thread.html#3120">[ thread ]</a>
  28               <a href="subject.html#3120">[ subject ]</a>
  29               <a href="author.html#3120">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i>IRCServices 5 has protocol modules which allow it to connect to many
  35 </I>&gt;<i>different kinds of ircds easily. Great idea. However, the core blatantly
  36 </I>&gt;<i>uses send_cmd, and makes assumptions about the format of specific
  37 </I>&gt;<i>commands,
  38 </I>
  39      This is by design.  The only reason for protocol modules in the first
  40 place is to kludge around variations in what ought to be a standard.  If
  41 you have an ircd that's so bizarre it can't even understand a NOTICE
  42 message, then Services won't support it.  Sorry, but I don't have the time
  43 or interest to deal with such software.
  44
  45   --Andrew Church
  46     <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  47     <A HREF="http://achurch.org/">http://achurch.org/</A>
  48 </PRE>
  49
  50
  51 <!--endarticle-->
  52     <HR>
  53     <P><UL>
  54         <!--threads-->
  55         <LI>Previous message: <A HREF="003119.html">[IRCServices Coding] send_cmd in non-protocol modules
  56 </A></li>
  57         <LI>Next message: <A HREF="003121.html">[IRCServices Coding] send_cmd in non-protocol modules
  58 </A></li>
  59          <LI> <B>Messages sorted by:</B>
  60               <a href="date.html#3120">[ date ]</a>
  61               <a href="thread.html#3120">[ thread ]</a>
  62               <a href="subject.html#3120">[ subject ]</a>
  63               <a href="author.html#3120">[ author ]</a>
  64          </LI>
  65        </UL>
  66
  67 </body></html>