]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000564.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2000 / 000564.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] New services implementations &amp; Updates?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20services%20implementations%20%26%20Updates%3F&In-Reply-To=l03130301b558cf5370fc%40%5B10.38.239.101%5D">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="000558.html">
11 <LINK REL="Next" HREF="000566.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] New services implementations &amp; Updates?</H1>
15 <B>Andrew Kempe</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20services%20implementations%20%26%20Updates%3F&In-Reply-To=l03130301b558cf5370fc%40%5B10.38.239.101%5D"
17 TITLE="[IRCServices] New services implementations &amp; Updates?">andrewk at icon.co.za
18 </A><BR>
19 <I>Fri Jun 2 12:39:54 PDT 2000</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000558.html">[IRCServices] New services implementations &amp; Updates?
22 </A></li>
23 <LI>Next message: <A HREF="000566.html">[IRCServices] New services implementations &amp; Updates?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#564">[ date ]</a>
27 <a href="thread.html#564">[ thread ]</a>
28 <a href="subject.html#564">[ subject ]</a>
29 <a href="author.html#564">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>This is a general reply to all the posts...
35
36 I think an SQL server would be a more robust storage method than the flat
37 files we use at present. I don't think we should replace them all together.
38 I would like an interface implemented in such a way that services writes
39 (saves) data and reads (loads) data in a fixed manner that is independant of
40 the method used to actually store it. This would allow people to implement a
41 variety of different storage mechanisms that are invisible to services. In
42 the end, services would be ignorant as to how or where it's data comes from
43 or goes to. This I hope will become a reality when modules are implemented.
44
45 Maybe someone wants to implement, dare I say it, an XML interface? :)
46
47 Andrew
48
49 &gt;<i> -----Original Message-----
50 </I>&gt;<i> From: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at delirious.shadowfire.org</A>
51 </I>&gt;<i> [mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at delirious.shadowfire.org</A>]On Behalf Of Jonathan
52 </I>&gt;<i> Morton
53 </I>&gt;<i> Sent: 30 May 2000 03:59
54 </I>&gt;<i> To: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at delirious.shadowfire.org</A>
55 </I>&gt;<i> Subject: Re: [IRCServices] New services implementations &amp; Updates?
56 </I>&gt;<i>
57 </I>&gt;<i>
58 </I>&gt;<i> &gt;The idea of using SQL sounds good at first. But these services
59 </I>&gt;<i> are generally
60 </I>&gt;<i> &gt;used by small or medium IRC networks all over the world. Some of
61 </I>&gt;<i> them have
62 </I>&gt;<i> &gt;low configurations and smaller bandwidths. These implementation
63 </I>&gt;<i> would need
64 </I>&gt;<i> &gt;an additional SQL server as Andy pointed out. Also having
65 </I>&gt;<i> statistics on web
66 </I>&gt;<i> &gt;would result to another performance decrease. Security is another point.
67 </I>&gt;<i>
68 </I>&gt;<i> Might I suggest a compromise, which would allow the increased Web
69 </I>&gt;<i> functionality while retaining the simplicity of the existing system:
70 </I>&gt;<i>
71 </I>&gt;<i> When a change is made to the Services database, export that change to an
72 </I>&gt;<i> OPTIONAL SQL database, which may or may not be on a different
73 </I>&gt;<i> server. Then
74 </I>&gt;<i> the Web-functionality can be stuck on top of that SQL database as
75 </I>&gt;<i> required.
76 </I>&gt;<i> If changes need to be made in the reverse direction too, then a mechanism
77 </I>&gt;<i> for re-importing changes should be made available.
78 </I>&gt;<i>
79 </I>&gt;<i> I think they key issue here is to avoid changing the basic implementation
80 </I>&gt;<i> where possible, but provide hooks so that bigger functionality
81 </I>&gt;<i> can be added
82 </I>&gt;<i> as and when it is desired, and can be set up by the server owners. I
83 </I>&gt;<i> really like the way Services can be set up with minimal effort - I gather
84 </I>&gt;<i> setting up SQL is rather less trivial. By making SQL optional,
85 </I>&gt;<i> we can grab
86 </I>&gt;<i> that extra functionality for those that want it (we probably don't, on our
87 </I>&gt;<i> small server) but keep it simple for those that don't. As for security,
88 </I>&gt;<i> that would need to be addressed by whoever decided to activate the SQL
89 </I>&gt;<i> setup - basic functionality should not be affected.
90 </I>&gt;<i>
91 </I>&gt;<i> --------------------------------------------------------------
92 </I>&gt;<i> from: Jonathan &quot;Chromatix&quot; Morton
93 </I>&gt;<i> mail: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">chromi at cyberspace.org</A> (not for attachments)
94 </I>&gt;<i> uni-mail: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">j.d.morton at lancaster.ac.uk</A>
95 </I>&gt;<i>
96 </I>&gt;<i> The key to knowledge is not to rely on people to teach you it.
97 </I>&gt;<i> --------------------------------------------------------------
98 </I>&gt;<i> Contributing to the VNC Project - &lt;A HREF=&quot;<A HREF="http://www.uk.research.att.com/vnc/&quot;">http://www.uk.research.att.com/vnc/&quot;</A>&gt;<A HREF="http://www.uk.research.att.com/vnc/&lt;/A">http://www.uk.research.att.com/vnc/&lt;/A</A>&gt;
99 </I>&gt;<i> Macintosh VNCserver v3.3.2 beta2.3 now posted at:
100 </I>&gt;<i> &lt;A HREF=&quot;<A HREF="http://chromatix.autistics.org/vnc/&quot;">http://chromatix.autistics.org/vnc/&quot;</A>&gt;<A HREF="http://chromatix.autistics.org/vnc/&lt;/A">http://chromatix.autistics.org/vnc/&lt;/A</A>&gt;
101 </I>&gt;<i>
102 </I>&gt;<i>
103 </I>&gt;<i>
104 </I>&gt;<i> ---------------------------------------------------------------
105 </I>&gt;<i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
106 </I>&gt;<i> with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
107 </I>&gt;<i>
108 </I>
109
110 ---------------------------------------------------------------
111 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
112 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
113
114
115 </PRE>
116
117 <!--endarticle-->
118 <HR>
119 <P><UL>
120 <!--threads-->
121 <LI>Previous message: <A HREF="000558.html">[IRCServices] New services implementations &amp; Updates?
122 </A></li>
123 <LI>Next message: <A HREF="000566.html">[IRCServices] New services implementations &amp; Updates?
124 </A></li>
125 <LI> <B>Messages sorted by:</B>
126 <a href="date.html#564">[ date ]</a>
127 <a href="thread.html#564">[ thread ]</a>
128 <a href="subject.html#564">[ subject ]</a>
129 <a href="author.html#564">[ author ]</a>
130 </LI>
131 </UL>
132
133 </body></html>