]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000839.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2000 / 000839.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] cheers. ideas.
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20cheers.%20ideas.&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="000853.html">
11 <LINK REL="Next" HREF="000840.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] cheers. ideas.</H1>
15 <B>&amp;quot</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20cheers.%20ideas.&In-Reply-To="
17 TITLE="[IRCServices] cheers. ideas.">&amp;quot
18 </A><BR>
19 <I>Wed Oct 11 09:19:39 PDT 2000</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000853.html">[IRCServices] Desperate Problems
22 </A></li>
23 <LI>Next message: <A HREF="000840.html">[IRCServices] cheers. ideas.
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#839">[ date ]</a>
27 <a href="thread.html#839">[ thread ]</a>
28 <a href="subject.html#839">[ subject ]</a>
29 <a href="author.html#839">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>its me again..
35
36 the data storage, using sql brings a lot of new possibilitys, with real
37 databases 3rd party programs/sites may use and change the information, this
38 is really interesting, develop internet portals based on the users/channels
39 information, search for users with html forms, retrieve/change password..
40 integration is the main ideia.
41
42 im currently helping a irc network called BrasNet (Brazil), the nick.db have
43 nothing more than 98 MB.. this _really_ stress the box.. with an indexed
44 database the searches and querys about nicks and chans registrations and
45 passwords authentication would be much more reliable!
46
47 well.. post you comment..
48
49 who is the services coding leader? Hi mr coder! (exchange ideas..)
50
51 Cheers,
52
53 Bruno Lacerda
54 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">sniffer at sniffer.net</A>
55 <A HREF="http://sniffer.net">http://sniffer.net</A>
56
57 ----- Original Message -----
58 From: &quot;Chris Wiest&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">kwahraw at relic.net</A>&gt;
59 To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org</A>&gt;
60 Cc: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org</A>&gt;
61 Sent: Wednesday, October 11, 2000 10:09 AM
62 Subject: Re: [IRCServices] cheers. ideas.
63
64
65 &gt;<i> *shrug* perspectives and experience I suppose come into play here. While
66 </I>&gt;<i> it may be the o/s we are operating from, which is FreeBSD4.0 (I am
67 </I>&gt;<i> hesitant to move to 4.1, though the CD's are sitting on my desk at
68 </I>&gt;<i> work due to its relative newness, and some network issues I've had with
69 </I>&gt;<i> it on our development machine at work), 4.0 one would think would be able
70 </I>&gt;<i> to keep mysql up and running. The issue seems to come about with multiple
71 </I>&gt;<i> query requests and attempts to place entries into the database
72 </I>&gt;<i> simultaneously. Again, my point is an XML format would perhaps be the
73 </I>&gt;<i> better way to go, as it is not dependent on a 3rd party application
74 </I>&gt;<i> working properly. Even if you have not had issues with the application
75 </I>&gt;<i> itself, there is still the exposure that a third party application (your
76 </I>&gt;<i> sql program) could crash, which on a philosophical level (putting aside my
77 </I>&gt;<i> above mentioned personal problems with the application) is a bad way to
78 </I>&gt;<i> go. I am not saying not to go ahead with sql, I am just pointing out a
79 </I>&gt;<i> pretty clear downfall to doing so.
80 </I>&gt;<i>
81 </I>&gt;<i> --CDW
82 </I>&gt;<i>
83 </I>&gt;<i> On Wed, 11 Oct 2000, Scott Seufert wrote:
84 </I>&gt;<i>
85 </I>&gt;<i> &gt; At 07:33 AM 10/11/2000 -0400, you wrote:
86 </I>&gt;<i> &gt; &gt;i debated, and even played with storing/retreiving to mysql. The
87 </I>problem
88 &gt;<i> &gt; &gt;that I've found is that you then deal with ensuring the sql program is
89 </I>up
90 &gt;<i> &gt; &gt;and running, and sql tends to crash (we actually have a sql based
91 </I>program
92 &gt;<i> &gt; &gt;currently that has an average uptime of 2 to 3 days). I don't know if
93 </I>&gt;<i> &gt; &gt;anyone else has experienced this, however it seems to kinda be
94 </I>&gt;<i> &gt; &gt;standard. We deal with 1600 to 2000 users simultaneous, they tend to
95 </I>get
96 &gt;<i> &gt; &gt;pissy when our services go boom, and rightly so. I'm not saying not to
97 </I>&gt;<i> &gt; &gt;move to sql (though I'd say xml seems a better option), but I am saying
98 </I>&gt;<i> &gt; &gt;that given sql's uptime, it can be an issue.
99 </I>&gt;<i> &gt; &gt;
100 </I>&gt;<i> &gt; &gt;--CDW
101 </I>&gt;<i> &gt;
102 </I>&gt;<i> &gt; &lt;snip&gt;
103 </I>&gt;<i> &gt;
104 </I>&gt;<i> &gt; In my experience I have seen quite the opposite, SQL tends to be quite
105 </I>&gt;<i> &gt; stable. Offering reliable support for tens of thousands. This experience
106 </I>&gt;<i> &gt; includes mySQL and MS SQL.
107 </I>&gt;<i> &gt;
108 </I>&gt;<i> &gt; Scott Seufert
109 </I>&gt;<i> &gt; aka katsklaw
110 </I>&gt;<i> &gt; Server Admin
111 </I>&gt;<i> &gt; Excalibre.ShadowFire.Org
112 </I>&gt;<i> &gt;
113 </I>&gt;<i> &gt;
114 </I>&gt;<i> &gt; ---------------------------------------------------------------
115 </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>
116 </I>&gt;<i> &gt; with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
117 </I>&gt;<i> &gt;
118 </I>&gt;<i>
119 </I>&gt;<i>
120 </I>&gt;<i> ---------------------------------------------------------------
121 </I>&gt;<i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
122 </I>&gt;<i> with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
123 </I>&gt;<i>
124 </I>
125
126 ---------------------------------------------------------------
127 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
128 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
129
130
131 </PRE>
132
133 <!--endarticle-->
134 <HR>
135 <P><UL>
136 <!--threads-->
137 <LI>Previous message: <A HREF="000853.html">[IRCServices] Desperate Problems
138 </A></li>
139 <LI>Next message: <A HREF="000840.html">[IRCServices] cheers. ideas.
140 </A></li>
141 <LI> <B>Messages sorted by:</B>
142 <a href="date.html#839">[ date ]</a>
143 <a href="thread.html#839">[ thread ]</a>
144 <a href="subject.html#839">[ subject ]</a>
145 <a href="author.html#839">[ author ]</a>
146 </LI>
147 </UL>
148
149 </body></html>