]> jfr.im git - irc.git/blobdiff - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000565.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2000 / 000565.html
diff --git a/software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000565.html b/software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000565.html
new file mode 100644 (file)
index 0000000..8ddd602
--- /dev/null
@@ -0,0 +1,167 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+   <TITLE> [IRCServices] New services implementations &amp; Updates?
+   </TITLE>
+   <LINK REL="Index" HREF="index.html" >
+   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20services%20implementations%20%26%20Updates%3F&In-Reply-To=">
+   <META NAME="robots" CONTENT="index,nofollow">
+   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+   <LINK REL="Previous"  HREF="000566.html">
+   <LINK REL="Next"  HREF="000552.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+   <H1>[IRCServices] New services implementations &amp; Updates?</H1>
+    <B>Chris Knipe</B> 
+    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20services%20implementations%20%26%20Updates%3F&In-Reply-To="
+       TITLE="[IRCServices] New services implementations &amp; Updates?">cgknipe at mweb.co.za
+       </A><BR>
+    <I>Sun Jun  4 05:21:18 PDT 2000</I>
+    <P><UL>
+        <LI>Previous message: <A HREF="000566.html">[IRCServices] New services implementations &amp; Updates?
+</A></li>
+        <LI>Next message: <A HREF="000552.html">[IRCServices] New services implementations &amp; Updates?
+</A></li>
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#565">[ date ]</a>
+              <a href="thread.html#565">[ thread ]</a>
+              <a href="subject.html#565">[ subject ]</a>
+              <a href="author.html#565">[ author ]</a>
+         </LI>
+       </UL>
+    <HR>  
+<!--beginarticle-->
+<PRE>WAP Enabled NickServ ? :P *LOL*
+
+Chow
+Chris
+
+BTW, I'll be reading a bit deaper with more attention the replies received
+and perhaps come to a more &quot;rpbust &amp; complete&quot; scenario and implementations.
+I must admit however, I did *not* lookup on the actual performance loss /
+gain on SQL related databases and such, it was just an idea pondering in my
+head...
+
+
+----- Original Message -----
+From: Andrew Kempe &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">andrewk at icon.co.za</A>&gt;
+To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at delirious.shadowfire.org</A>&gt;
+Sent: 02 June 2000 09:39
+Subject: RE: [IRCServices] New services implementations &amp; Updates?
+
+
+&gt;<i> This is a general reply to all the posts...
+</I>&gt;<i>
+</I>&gt;<i> I think an SQL server would be a more robust storage method than the flat
+</I>&gt;<i> files we use at present. I don't think we should replace them all
+</I>together.
+&gt;<i> I would like an interface implemented in such a way that services writes
+</I>&gt;<i> (saves) data and reads (loads) data in a fixed manner that is independant
+</I>of
+&gt;<i> the method used to actually store it. This would allow people to implement
+</I>a
+&gt;<i> variety of different storage mechanisms that are invisible to services. In
+</I>&gt;<i> the end, services would be ignorant as to how or where it's data comes
+</I>from
+&gt;<i> or goes to. This I hope will become a reality when modules are
+</I>implemented.
+&gt;<i>
+</I>&gt;<i> Maybe someone wants to implement, dare I say it, an XML interface? :)
+</I>&gt;<i>
+</I>&gt;<i> Andrew
+</I>&gt;<i>
+</I>&gt;<i> &gt; -----Original Message-----
+</I>&gt;<i> &gt; From: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at delirious.shadowfire.org</A>
+</I>&gt;<i> &gt; [mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at delirious.shadowfire.org</A>]On Behalf Of Jonathan
+</I>&gt;<i> &gt; Morton
+</I>&gt;<i> &gt; Sent: 30 May 2000 03:59
+</I>&gt;<i> &gt; To: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at delirious.shadowfire.org</A>
+</I>&gt;<i> &gt; Subject: Re: [IRCServices] New services implementations &amp; Updates?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; &gt;The idea of using SQL sounds good at first. But these services
+</I>&gt;<i> &gt; are generally
+</I>&gt;<i> &gt; &gt;used by small or medium IRC networks all over the world. Some of
+</I>&gt;<i> &gt; them have
+</I>&gt;<i> &gt; &gt;low configurations and smaller bandwidths. These implementation
+</I>&gt;<i> &gt; would need
+</I>&gt;<i> &gt; &gt;an additional SQL server as Andy pointed out. Also having
+</I>&gt;<i> &gt; statistics on web
+</I>&gt;<i> &gt; &gt;would result to another performance decrease. Security is another
+</I>point.
+&gt;<i> &gt;
+</I>&gt;<i> &gt; Might I suggest a compromise, which would allow the increased Web
+</I>&gt;<i> &gt; functionality while retaining the simplicity of the existing system:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; When a change is made to the Services database, export that change to an
+</I>&gt;<i> &gt; OPTIONAL SQL database, which may or may not be on a different
+</I>&gt;<i> &gt; server.  Then
+</I>&gt;<i> &gt; the Web-functionality can be stuck on top of that SQL database as
+</I>&gt;<i> &gt; required.
+</I>&gt;<i> &gt; If changes need to be made in the reverse direction too, then a
+</I>mechanism
+&gt;<i> &gt; for re-importing changes should be made available.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I think they key issue here is to avoid changing the basic
+</I>implementation
+&gt;<i> &gt; where possible, but provide hooks so that bigger functionality
+</I>&gt;<i> &gt; can be added
+</I>&gt;<i> &gt; as and when it is desired, and can be set up by the server owners.  I
+</I>&gt;<i> &gt; really like the way Services can be set up with minimal effort - I
+</I>gather
+&gt;<i> &gt; setting up SQL is rather less trivial.  By making SQL optional,
+</I>&gt;<i> &gt; we can grab
+</I>&gt;<i> &gt; that extra functionality for those that want it (we probably don't, on
+</I>our
+&gt;<i> &gt; small server) but keep it simple for those that don't.  As for security,
+</I>&gt;<i> &gt; that would need to be addressed by whoever decided to activate the SQL
+</I>&gt;<i> &gt; setup - basic functionality should not be affected.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; --------------------------------------------------------------
+</I>&gt;<i> &gt; from:     Jonathan &quot;Chromatix&quot; Morton
+</I>&gt;<i> &gt; mail:     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">chromi at cyberspace.org</A>  (not for attachments)
+</I>&gt;<i> &gt; uni-mail: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">j.d.morton at lancaster.ac.uk</A>
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; The key to knowledge is not to rely on people to teach you it.
+</I>&gt;<i> &gt; --------------------------------------------------------------
+</I>&gt;<i> &gt; Contributing to the VNC Project - &lt;A  HREF=&quot;<A HREF="http://www.uk.research.att.com/vnc/&quot;">http://www.uk.research.att.com/vnc/&quot;</A>&gt;<A HREF="http://www.uk.research.att.com/vnc/&lt;/A">http://www.uk.research.att.com/vnc/&lt;/A</A>&gt;
+</I>&gt;<i> &gt; Macintosh VNCserver v3.3.2 beta2.3 now posted at:
+</I>&gt;<i> &gt; &lt;A  HREF=&quot;<A HREF="http://chromatix.autistics.org/vnc/&quot;">http://chromatix.autistics.org/vnc/&quot;</A>&gt;<A HREF="http://chromatix.autistics.org/vnc/&lt;/A">http://chromatix.autistics.org/vnc/&lt;/A</A>&gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; ---------------------------------------------------------------
+</I>&gt;<i> &gt; To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
+</I>&gt;<i> &gt; with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
+</I>&gt;<i> &gt;
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> ---------------------------------------------------------------
+</I>&gt;<i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
+</I>&gt;<i> with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
+</I>
+
+---------------------------------------------------------------
+To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
+with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
+
+
+</PRE>
+
+<!--endarticle-->
+    <HR>
+    <P><UL>
+        <!--threads-->
+       <LI>Previous message: <A HREF="000566.html">[IRCServices] New services implementations &amp; Updates?
+</A></li>
+       <LI>Next message: <A HREF="000552.html">[IRCServices] New services implementations &amp; Updates?
+</A></li>
+         <LI> <B>Messages sorted by:</B> 
+              <a href="date.html#565">[ date ]</a>
+              <a href="thread.html#565">[ thread ]</a>
+              <a href="subject.html#565">[ subject ]</a>
+              <a href="author.html#565">[ author ]</a>
+         </LI>
+       </UL>
+
+</body></html>