software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001442.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] SGLINE
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20SGLINE&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="001440.html">
  11    <LINK REL="Next"  HREF="001444.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] SGLINE</H1>
  15     <B>Dr. K. Hawkes</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20SGLINE&In-Reply-To="
  17        TITLE="[IRCServices] SGLINE">k.hawkes at zombies.force9.net
  18        </A><BR>
  19     <I>Sun Feb 18 05:32:25 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001440.html">AW: [IRCServices] SGLINE
  22 </A></li>
  23         <LI>Next message: <A HREF="001444.html">[IRCServices] Minor Cosmetics and Sglines
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1442">[ date ]</a>
  27               <a href="thread.html#1442">[ thread ]</a>
  28               <a href="subject.html#1442">[ subject ]</a>
  29               <a href="author.html#1442">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> &gt; I think this is why there are plans to modularize(sp?) the code so that
  35 </I>&gt;<i> &gt; it will be easier in the future to support the daemon that your network
  36 </I>&gt;<i> &gt; chooses.
  37 </I>&gt;<i>
  38 </I>&gt;<i> That'd be a great idea, that way all you build is the core code, then any
  39 </I>&gt;<i> &quot;plugins&quot; which would stand betweeen Services and possibly the socket
  40 </I>code
  41 &gt;<i> to the daemon, or perhaps directly to the daemon itself.
  42 </I>&gt;<i>
  43 </I>&gt;<i> Hell, a lot of the functions themselves could even be modularized, too.
  44 </I>&gt;<i> Want something in your Services?  Edit the config file.  And there you
  45 </I>go!
  46 &gt;<i> Apache is a great example of this kind of stuff with its DSO support,
  47 </I>&gt;<i> including stuff like mod_access, and the various mod_auth* modules, like
  48 </I>&gt;<i> RADIUS, TACACS, system, etc.
  49 </I>&gt;<i>
  50 </I>&gt;<i> Thing is, the dl_* family of functions may work differently on many
  51 </I>&gt;<i> platforms. Plus on some systems, compiling shared libraries is a
  52 </I>different
  53 &gt;<i> or possibly difficult exercise on some systems, e.g. BSDI which uses an
  54 </I>&gt;<i> entirely different compiler (based on what I've read in other packages,
  55 </I>&gt;<i> e.g. Listar, which also uses this model for some of its support, which
  56 </I>&gt;<i> could also include support for talking directly to an MTA's mail queue
  57 </I>&gt;<i> space).
  58 </I>&gt;<i>
  59 </I>&gt;<i> In those situations where compiling shared libraries is a pain or is
  60 </I>&gt;<i> outright impossible, compiling static support for a given daemon should
  61 </I>&gt;<i> still be considered an option.
  62 </I>&gt;<i>
  63 </I>&gt;<i> My knowledge in actual coding for this is a bit lacking, but just
  64 </I>throwing
  65 &gt;<i> my thoughts of how I've seen stuff done elsewhere. :)  Andy?
  66 </I>&gt;<i>
  67 </I>&gt;<i> --Ian R. Justman, Co-Founder and Postmaster, The EsperNet IRC Network.
  68 </I>&gt;<i>
  69 </I>
  70 Yeah, modularising the code would make adding things to IRCServices alot
  71 easier but coding it wouldn't be the easiest of things possible.  Far
  72 beyond my knowledge and expertise.
  73
  74 Eggdrop (the IRC bot) is modularised, it has '.mod' plugins which are
  75 written in C and allow you to add extra functionality to the bot... is this
  76 how you plan to modularise IRCServices?
  77
  78 As for static and shared libraries, Eggdrop if I recall allows you to
  79 compile statically or dynamically... statically doesn't allow the
  80 loading/unloading of modules but dynamically does if I recall, I could be
  81 wrong here.
  82
  83 Just my 0.2 pence.
  84
  85 Quinn
  86
  87
  88 </PRE>
  89
  90 <!--endarticle-->
  91     <HR>
  92     <P><UL>
  93         <!--threads-->
  94         <LI>Previous message: <A HREF="001440.html">AW: [IRCServices] SGLINE
  95 </A></li>
  96         <LI>Next message: <A HREF="001444.html">[IRCServices] Minor Cosmetics and Sglines
  97 </A></li>
  98          <LI> <B>Messages sorted by:</B>
  99               <a href="date.html#1442">[ date ]</a>
 100               <a href="thread.html#1442">[ thread ]</a>
 101               <a href="subject.html#1442">[ subject ]</a>
 102               <a href="author.html#1442">[ author ]</a>
 103          </LI>
 104        </UL>
 105
 106 </body></html>