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

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Possible new callback on AUTH
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20Possible%20new%20callback%20on%20AUTH&In-Reply-To=430aa265.12540%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="003150.html">
  11    <LINK REL="Next"  HREF="003152.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Possible new callback on AUTH</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20Possible%20new%20callback%20on%20AUTH&In-Reply-To=430aa265.12540%40msgid.achurch.org"
  17        TITLE="[IRCServices Coding] Possible new callback on AUTH">achurch at achurch.org
  18        </A><BR>
  19     <I>Tue Aug 23 13:24:00 PDT 2005</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003150.html">[IRCServices Coding] Possible new callback on AUTH
  22 </A></li>
  23         <LI>Next message: <A HREF="003152.html">[IRCServices Coding] Possible new callback on AUTH
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3151">[ date ]</a>
  27               <a href="thread.html#3151">[ thread ]</a>
  28               <a href="subject.html#3151">[ subject ]</a>
  29               <a href="author.html#3151">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;&gt;<i>I'm working on a bit of a module to orient new users, but (with spambots
  35 </I>&gt;&gt;<i>and stuff) it's a little inconvenient to do this with the register callback.
  36 </I>&gt;&gt;<i>
  37 </I>&gt;&gt;<i>Not wanting to fork the codebase, would it be at all possible to get a
  38 </I>&gt;&gt;<i>new callback on NS AUTH?
  39 </I>&gt;<i>
  40 </I>&gt;<i>     Ordinarily I'd want to wait for 5.1, but seeing as the 5.1 alpha is
  41 </I>&gt;<i>already several lifetimes later than I'd hoped, why not? (:  I'll add it
  42 </I>&gt;<i>for the next 5.0 release.
  43 </I>
  44      Actually I guess I should ask: where do you need the callback?  Is it
  45 sufficient to have it called after all normal processing, or do you want to
  46 replace part of the normal AUTH processing?
  47
  48   --Andrew Church
  49     <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  50     <A HREF="http://achurch.org/">http://achurch.org/</A>
  51 </PRE>
  52
  53
  54 <!--endarticle-->
  55     <HR>
  56     <P><UL>
  57         <!--threads-->
  58         <LI>Previous message: <A HREF="003150.html">[IRCServices Coding] Possible new callback on AUTH
  59 </A></li>
  60         <LI>Next message: <A HREF="003152.html">[IRCServices Coding] Possible new callback on AUTH
  61 </A></li>
  62          <LI> <B>Messages sorted by:</B>
  63               <a href="date.html#3151">[ date ]</a>
  64               <a href="thread.html#3151">[ thread ]</a>
  65               <a href="subject.html#3151">[ subject ]</a>
  66               <a href="author.html#3151">[ author ]</a>
  67          </LI>
  68        </UL>
  69
  70 </body></html>