]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001795.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001795.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=200212191833.gBJIX7C01586%40localhost.localdomain">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001794.html">
11 <LINK REL="Next" HREF="001796.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] New IRC Services project</H1>
15 <B>Finny Merrill</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20New%20IRC%20Services%20project&In-Reply-To=200212191833.gBJIX7C01586%40localhost.localdomain"
17 TITLE="[IRCServices Coding] New IRC Services project">griever at t2n.org
18 </A><BR>
19 <I>Thu Dec 19 12:46:30 PST 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001794.html">[IRCServices Coding] New IRC Services project
22 </A></li>
23 <LI>Next message: <A HREF="001796.html">[IRCServices Coding] New IRC Services project
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1795">[ date ]</a>
27 <a href="thread.html#1795">[ thread ]</a>
28 <a href="subject.html#1795">[ subject ]</a>
29 <a href="author.html#1795">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>On Thu, 19 Dec 2002, Craig Edwards wrote:
35
36 &gt;<i> 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.
37 </I>&gt;<i>
38 </I>Don't top post, please add newlines.
39
40 This is why you would implement a memory cache. Dalnet doesn't seem to
41 have a problem with it and they use SQL databases...
42
43
44 </PRE>
45
46 <!--endarticle-->
47 <HR>
48 <P><UL>
49 <!--threads-->
50 <LI>Previous message: <A HREF="001794.html">[IRCServices Coding] New IRC Services project
51 </A></li>
52 <LI>Next message: <A HREF="001796.html">[IRCServices Coding] New IRC Services project
53 </A></li>
54 <LI> <B>Messages sorted by:</B>
55 <a href="date.html#1795">[ date ]</a>
56 <a href="thread.html#1795">[ thread ]</a>
57 <a href="subject.html#1795">[ subject ]</a>
58 <a href="author.html#1795">[ author ]</a>
59 </LI>
60 </UL>
61
62 </body></html>