software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000246.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Services 5 - Suggestions/Queries
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205%20-%20Suggestions/Queries&In-Reply-To=8CC04B5C-1D5A-11D6-AA9A-003065BD4458%40sogno.net">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="000245.html">
  11    <LINK REL="Next"  HREF="000247.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Services 5 - Suggestions/Queries</H1>
  15     <B>Mark Hetherington</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205%20-%20Suggestions/Queries&In-Reply-To=8CC04B5C-1D5A-11D6-AA9A-003065BD4458%40sogno.net"
  17        TITLE="[IRCServices Coding] Services 5 - Suggestions/Queries">mark at mhetherington.demon.co.uk
  18        </A><BR>
  19     <I>Sat Feb  9 18:37:18 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000245.html">[IRCServices Coding] Services 5.0 alpha 20 -- you know you want it
  22 </A></li>
  23         <LI>Next message: <A HREF="000247.html">[IRCServices Coding] Services 5 - Suggestions/Queries
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#246">[ date ]</a>
  27               <a href="thread.html#246">[ thread ]</a>
  28               <a href="subject.html#246">[ subject ]</a>
  29               <a href="author.html#246">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>1) Suggestion: When a qline is set on the ircd, the error reported to the
  35 user is formatted as follows:
  36
  37 Guest781361765 Erroneous Nickname: Reserved for Services
  38
  39 However, sqlines set in services merely report:
  40
  41 testsqline Erroneous Nickname: Reserved nickname
  42
  43 A better response would be:
  44
  45 testsqline Erroneous Nickname: (reason set in services)
  46
  47 2) Suggestion/Query: The sline modules provides a very useful central
  48 repository for qlines/zlines etc that remove the need for individual
  49 ircd.conf changes when a new sline is required. However, in the qline
  50 example above, services does not seem to have added the qline to the list
  51 used by the ircd. In the event of any downtime, this would mean that the
  52 qlines would no longer remain in operation even though some services set
  53 options (e.g. akills) would likely survive the downtime. I appreciate that
  54 this maybe be largely an IRCd issue but if services were to provide a
  55 framework for interaction with the IRCd, I am sure it should be possible to
  56 add IRCd level support so identifying the appropriate area would be a good
  57 first step.
  58
  59 3) Suggestion/Query: With the s(z)line support, I am not sure of the exact
  60 manner in which Services determines what level of support is available in
  61 the ircd (i.e. whether it is the appropriate protocol module or the sline
  62 module which makes the decision and how).
  63
  64 I notice for Unreal, services reports in the log a lack of IP information as
  65 being of relevance to the szline support. If this is determined by say the
  66 protocol module, then I guess the operation is fixed by that module, but if
  67 it is down to some sort of real time startup test, I would assume that the
  68 Unreal &quot;connection message&quot; which is lacking in IP is the cause. Since this
  69 is a relatively trivial issue to address on the IRCd, it would be useful to
  70 have some way to have services recognise the support.
  71
  72 This largely depends on the method(s) services uses to determine the level
  73 of support. If the protocol module does fix this operation, the suggestion
  74 would be to have some type of configuration directive to override this
  75 operation for a server modified to be more &quot;services friendly&quot;.
  76
  77 If it does check the connection message format, I can safely update that
  78 portion of code and services have access to IP addresses in the manner it
  79 desires. A number of &quot;tools&quot; cite Unreal's connection message as a bug so it
  80 may ultimately be addressed in the new version as it progresses through
  81 beta.
  82
  83 However, if neither of these options is in force, then I guess I am loooking
  84 for some long term solution to this based on how the current operation
  85 determines support.
  86
  87
  88 Mark.
  89
  90
  91 </PRE>
  92
  93 <!--endarticle-->
  94     <HR>
  95     <P><UL>
  96         <!--threads-->
  97         <LI>Previous message: <A HREF="000245.html">[IRCServices Coding] Services 5.0 alpha 20 -- you know you want it
  98 </A></li>
  99         <LI>Next message: <A HREF="000247.html">[IRCServices Coding] Services 5 - Suggestions/Queries
 100 </A></li>
 101          <LI> <B>Messages sorted by:</B>
 102               <a href="date.html#246">[ date ]</a>
 103               <a href="thread.html#246">[ thread ]</a>
 104               <a href="subject.html#246">[ subject ]</a>
 105               <a href="author.html#246">[ author ]</a>
 106          </LI>
 107        </UL>
 108
 109 </body></html>