]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
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>&quot</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20cheers.%20ideas.&In-Reply-To=" | |
17 | TITLE="[IRCServices] cheers. ideas.">&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: "Chris Wiest" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">kwahraw at relic.net</A>> | |
59 | To: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org</A>> | |
60 | Cc: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org</A>> | |
61 | Sent: Wednesday, October 11, 2000 10:09 AM | |
62 | Subject: Re: [IRCServices] cheers. ideas. | |
63 | ||
64 | ||
65 | ><i> *shrug* perspectives and experience I suppose come into play here. While | |
66 | </I>><i> it may be the o/s we are operating from, which is FreeBSD4.0 (I am | |
67 | </I>><i> hesitant to move to 4.1, though the CD's are sitting on my desk at | |
68 | </I>><i> work due to its relative newness, and some network issues I've had with | |
69 | </I>><i> it on our development machine at work), 4.0 one would think would be able | |
70 | </I>><i> to keep mysql up and running. The issue seems to come about with multiple | |
71 | </I>><i> query requests and attempts to place entries into the database | |
72 | </I>><i> simultaneously. Again, my point is an XML format would perhaps be the | |
73 | </I>><i> better way to go, as it is not dependent on a 3rd party application | |
74 | </I>><i> working properly. Even if you have not had issues with the application | |
75 | </I>><i> itself, there is still the exposure that a third party application (your | |
76 | </I>><i> sql program) could crash, which on a philosophical level (putting aside my | |
77 | </I>><i> above mentioned personal problems with the application) is a bad way to | |
78 | </I>><i> go. I am not saying not to go ahead with sql, I am just pointing out a | |
79 | </I>><i> pretty clear downfall to doing so. | |
80 | </I>><i> | |
81 | </I>><i> --CDW | |
82 | </I>><i> | |
83 | </I>><i> On Wed, 11 Oct 2000, Scott Seufert wrote: | |
84 | </I>><i> | |
85 | </I>><i> > At 07:33 AM 10/11/2000 -0400, you wrote: | |
86 | </I>><i> > >i debated, and even played with storing/retreiving to mysql. The | |
87 | </I>problem | |
88 | ><i> > >that I've found is that you then deal with ensuring the sql program is | |
89 | </I>up | |
90 | ><i> > >and running, and sql tends to crash (we actually have a sql based | |
91 | </I>program | |
92 | ><i> > >currently that has an average uptime of 2 to 3 days). I don't know if | |
93 | </I>><i> > >anyone else has experienced this, however it seems to kinda be | |
94 | </I>><i> > >standard. We deal with 1600 to 2000 users simultaneous, they tend to | |
95 | </I>get | |
96 | ><i> > >pissy when our services go boom, and rightly so. I'm not saying not to | |
97 | </I>><i> > >move to sql (though I'd say xml seems a better option), but I am saying | |
98 | </I>><i> > >that given sql's uptime, it can be an issue. | |
99 | </I>><i> > > | |
100 | </I>><i> > >--CDW | |
101 | </I>><i> > | |
102 | </I>><i> > <snip> | |
103 | </I>><i> > | |
104 | </I>><i> > In my experience I have seen quite the opposite, SQL tends to be quite | |
105 | </I>><i> > stable. Offering reliable support for tens of thousands. This experience | |
106 | </I>><i> > includes mySQL and MS SQL. | |
107 | </I>><i> > | |
108 | </I>><i> > Scott Seufert | |
109 | </I>><i> > aka katsklaw | |
110 | </I>><i> > Server Admin | |
111 | </I>><i> > Excalibre.ShadowFire.Org | |
112 | </I>><i> > | |
113 | </I>><i> > | |
114 | </I>><i> > --------------------------------------------------------------- | |
115 | </I>><i> > To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A> | |
116 | </I>><i> > with "unsubscribe ircservices" in the body, without the quotes. | |
117 | </I>><i> > | |
118 | </I>><i> | |
119 | </I>><i> | |
120 | </I>><i> --------------------------------------------------------------- | |
121 | </I>><i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A> | |
122 | </I>><i> with "unsubscribe ircservices" in the body, without the quotes. | |
123 | </I>><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 "unsubscribe ircservices" 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> |