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

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Feature Request
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20Request&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="000579.html">
  11    <LINK REL="Next"  HREF="000584.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Feature Request</H1>
  15     <B>Russ Garrett</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20Request&In-Reply-To="
  17        TITLE="[IRCServices Coding] Feature Request">rg at tcslon.com
  18        </A><BR>
  19     <I>Tue Apr 23 12:42:14 PDT 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000579.html">[IRCServices Coding] Feature Request
  22 </A></li>
  23         <LI>Next message: <A HREF="000584.html">[IRCServices Coding] Feature Request
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#580">[ date ]</a>
  27               <a href="thread.html#580">[ thread ]</a>
  28               <a href="subject.html#580">[ subject ]</a>
  29               <a href="author.html#580">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Tom Moyer wrote:
  35
  36 &gt;<i>So not talking about the java Chat side, what about Registering Nicknames
  37 </I>&gt;<i>online, and possibly having a memo Retrival system online.  So it can be
  38 </I>&gt;<i>accessed Via HTTP?
  39 </I>&gt;<i>
  40 </I>&gt;<i>
  41 </I>I think it raises the same point - to be honest I don't like a web
  42 interface on the end of services at all - IMHO any external (non-IRC)
  43 access should be on another heavily-access-controlled end of the
  44 database. Although I have all faith in Andy's web server coding, I'd
  45 rather my web access was done by a web server, and my IRC services
  46 handled by services, both sharing a common database backend (any news on
  47 the MySql plugin? ;) - this is the whole point in unix in general - many
  48 specialist programs working together, to a better (faster, more secure)
  49 end than one large behemoth of a services/web server/microwave/kitchen
  50 sink.
  51
  52 BTW, I haven't been around much because we've merged with some friends'
  53 net, who run Epona, so that spares you my endless XML nit-picking until
  54 I can convert them to IRCServices (&quot;friends don't let friends use Epona&quot; ;).
  55
  56 Russ Garrett (<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">russ at garrett.co.uk</A>)
  57 Shameless Plug: <A HREF="http://www.faereal.net">http://www.faereal.net</A>
  58
  59
  60 </PRE>
  61
  62 <!--endarticle-->
  63     <HR>
  64     <P><UL>
  65         <!--threads-->
  66         <LI>Previous message: <A HREF="000579.html">[IRCServices Coding] Feature Request
  67 </A></li>
  68         <LI>Next message: <A HREF="000584.html">[IRCServices Coding] Feature Request
  69 </A></li>
  70          <LI> <B>Messages sorted by:</B>
  71               <a href="date.html#580">[ date ]</a>
  72               <a href="thread.html#580">[ thread ]</a>
  73               <a href="subject.html#580">[ subject ]</a>
  74               <a href="author.html#580">[ author ]</a>
  75          </LI>
  76        </UL>
  77
  78 </body></html>