]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/002517.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 002517.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> AW: AW: [IRCServices] Backup databases?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20AW%3A%20%5BIRCServices%5D%20Backup%20databases%3F&In-Reply-To=002701c16c8f%24c83e3e10%24c901a8c0%40murphy">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="002516.html">
11 <LINK REL="Next" HREF="002519.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>AW: AW: [IRCServices] Backup databases?</H1>
15 <B>Duane Groth</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20AW%3A%20%5BIRCServices%5D%20Backup%20databases%3F&In-Reply-To=002701c16c8f%24c83e3e10%24c901a8c0%40murphy"
17 TITLE="AW: AW: [IRCServices] Backup databases?">duane at groth.net
18 </A><BR>
19 <I>Wed Nov 14 01:06:01 PST 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002516.html">AW: AW: [IRCServices] Backup databases?
22 </A></li>
23 <LI>Next message: <A HREF="002519.html">AW: AW: [IRCServices] Backup databases?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2517">[ date ]</a>
27 <a href="thread.html#2517">[ thread ]</a>
28 <a href="subject.html#2517">[ subject ]</a>
29 <a href="author.html#2517">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Hello Chris,
35
36 Well if we're going to hypothesis on web based user admin of services,
37 why not super users, with SSL encryption? I mean instead of typing a
38 heap of commands, scrolling up and down, isn't it usually easier to
39 see all the options and information in front of you on one page?
40
41 Not to mention the fact that there are a large amount of IRC networks
42 running web interfaces with Java chat clients, wouldn't services web
43 interfaces be the logical next step?
44
45 My original statement only mentioned this as a side benefit, what I'm
46 really after is redundancy, or the very least automatic change over on
47 primary failure.
48
49 --
50 Best regards,
51 Duane mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">duane at groth.net</A>
52
53 Wednesday, November 14, 2001, 9:08:53 AM, you wrote:
54
55 &gt;&gt;<i> Buuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuut....Isn't the idea of
56 </I>&gt;&gt;<i> *IRC*Services, for them to be used on *IRC* Networks??
57 </I>&gt;&gt;<i> I was being sarcastic about editing thru web browser ;D
58 </I>&gt;&gt;<i>
59 </I>
60 CB&gt; Well you will use them on irc, but I see nothing wrong with doing the
61 CB&gt; admin on the web. I would assume more users would be familiar with web
62 CB&gt; interfaces than with sending chanserv/nickserv the commands. Not that
63 CB&gt; I'm saying ircservices should be changed this way, I just don't see
64 CB&gt; anything against it.
65
66
67 </PRE>
68
69 <!--endarticle-->
70 <HR>
71 <P><UL>
72 <!--threads-->
73 <LI>Previous message: <A HREF="002516.html">AW: AW: [IRCServices] Backup databases?
74 </A></li>
75 <LI>Next message: <A HREF="002519.html">AW: AW: [IRCServices] Backup databases?
76 </A></li>
77 <LI> <B>Messages sorted by:</B>
78 <a href="date.html#2517">[ date ]</a>
79 <a href="thread.html#2517">[ thread ]</a>
80 <a href="subject.html#2517">[ subject ]</a>
81 <a href="author.html#2517">[ author ]</a>
82 </LI>
83 </UL>
84
85 </body></html>