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

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] New IRC Services project
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20New%20IRC%20Services%20project&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="001790.html">
  11    <LINK REL="Next"  HREF="001792.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] New IRC Services project</H1>
  15     <B>Craig Edwards</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20New%20IRC%20Services%20project&In-Reply-To="
  17        TITLE="[IRCServices Coding] New IRC Services project">brain at brainbox.winbot.co.uk
  18        </A><BR>
  19     <I>Thu Dec 19 10:21:10 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001790.html">[IRCServices Coding] BotServ
  22 </A></li>
  23         <LI>Next message: <A HREF="001792.html">[IRCServices Coding] New IRC Services project
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1791">[ date ]</a>
  27               <a href="thread.html#1791">[ thread ]</a>
  28               <a href="subject.html#1791">[ subject ]</a>
  29               <a href="author.html#1791">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>MySQL databases arent really a good idea for an ircservices server on a large network - imagine the number of constant queries involved, it would be a much busier situation than many large websites, you would have to make a query for practically every RAW irc line from your uplink, e.g. for checking access, etc. If not for every RAW line, but for every MODE, JOIN, and PRIVMSG to a pseudoclient, and every connect, NICK, etc... Not to mention that MySQL's transaction support isnt that good (MySQL's one and only downfall) which would mean maybe a database such as PostgreSQL may work much better in this case. I have my doubts about performance though. Would connections to the database be persistent? Im not sure about the low level workings of DBMS systems but for this kind of application the connection would not need to be closed after each query, the slowdowns would be unbelievably slow.
  35
  36 &gt;<i>On Wed, Dec 18, 2002 at 09:38:58PM +0000, Craig McLure &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">Craig at chatspike.net</A>&gt; wrote:
  37 </I>&gt;&gt;<i> Just a note.. do you realise how dangerous MySQL databases are? a while back i was discussing with my staff the subject of making one, Can you garuntee that MySQL wont crash? can you be totally certain that no-one else can access your database and make significant changes? currently the &quot;FlatFiles&quot; are a much safer way to store information, and even if someone tries to modify them, its never easy.
  38 </I>&gt;<i>
  39 </I>&gt;<i>yes, and see how many important websites rely on mysql. MySQL 3.23 _is_
  40 </I>&gt;<i>stable.
  41 </I>&gt;<i>the goal is to allow others to access the database through websites, etc
  42 </I>&gt;<i>... and modify it. And yes, MySQL can be configured to restrict access to
  43 </I>&gt;<i>some people, with brand new techniques like login and password.
  44 </I>&gt;<i>
  45 </I>&gt;<i>I'm not sure mysql would be a solution though. postgres, with a set of
  46 </I>&gt;<i>stored procedures for external modification of the database, would
  47 </I>&gt;<i>probably be a better choice.
  48 </I>&gt;<i>
  49 </I>&gt;&gt;<i> And still, as always, i dont see the point in BotServ.
  50 </I>&gt;<i>
  51 </I>&gt;<i>yeah, you don't, but some people do.
  52 </I>&gt;<i>
  53 </I>&gt;<i>lucas
  54 </I>&gt;<i>------------------------------------------------------------------
  55 </I>&gt;<i>To unsubscribe or change your subscription options, visit:
  56 </I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
  57 </I>
  58
  59
  60 </PRE>
  61
  62 <!--endarticle-->
  63     <HR>
  64     <P><UL>
  65         <!--threads-->
  66         <LI>Previous message: <A HREF="001790.html">[IRCServices Coding] BotServ
  67 </A></li>
  68         <LI>Next message: <A HREF="001792.html">[IRCServices Coding] New IRC Services project
  69 </A></li>
  70          <LI> <B>Messages sorted by:</B>
  71               <a href="date.html#1791">[ date ]</a>
  72               <a href="thread.html#1791">[ thread ]</a>
  73               <a href="subject.html#1791">[ subject ]</a>
  74               <a href="author.html#1791">[ author ]</a>
  75          </LI>
  76        </UL>
  77
  78 </body></html>