software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000551.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=Pine.LNX.4.21.5204271851520.17542-100000%40fusion.sunnyline.co.za">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="000548.html">
  11    <LINK REL="Next"  HREF="000553.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] New services implementations &amp; Updates?</H1>
  15     <B>Jonathan George</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20New%20services%20implementations%20%26%20Updates%3F&In-Reply-To=Pine.LNX.4.21.5204271851520.17542-100000%40fusion.sunnyline.co.za"
  17        TITLE="[IRCServices] New services implementations &amp; Updates?">jonathan at lite.net
  18        </A><BR>
  19     <I>Sun May 28 09:05:06 PDT 2000</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000548.html">[IRCServices] combining services databases
  22 </A></li>
  23         <LI>Next message: <A HREF="000553.html">[IRCServices] New services implementations &amp; Updates?
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#551">[ date ]</a>
  27               <a href="thread.html#551">[ thread ]</a>
  28               <a href="subject.html#551">[ subject ]</a>
  29               <a href="author.html#551">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>   I'm only going to comment on the SQL database implementation idea.
  35
  36         I at one point, when writing a set of IRC services (from scratch)
  37 was going to use an SQL database.  Yes, a web interface like you describe
  38 is entirely possible (and a wonderful idea too, that was one of the main
  39 reasons I was going to use SQL).
  40
  41         But.  SQL will be no faster than keeping all records in a hash
  42 table like we do now.  Services is not a threaded process, so we won't be
  43 able to really make effective use of an SQL server, because it's designed
  44 to be a database which can be access and modified in parallel by two or
  45 more connections.  It just isn't worth the hassle of converting a *LOT* of
  46 code to using it.  In fact, it'd be a near rewrite of Services in itself
  47 just to add this feature -- all for what, a few webpages?
  48
  49         My suggestion would be to add support for a socket listen(2)ing
  50 and then have your CGI/PHP3/ASP/&lt;whatever&gt; connect to that socket and
  51 request information from the database, send updates.. . etc.
  52         If you were to do the above then the ideas are endless.  You could
  53 write a small program in VB which users could use to read memo's, be
  54 notified of when they have new memo's in an ICQ like interface, edit your
  55 user information.. . etc.  And most of all, you retain the original want:
  56 you want a web interface.
  57
  58
  59         Questions about how I implemented SQL with the services I wrote
  60 can be emailed to me...  I used MySQL in my design.
  61
  62 -----------------------------------------
  63 // Jonathan George   : <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">jonathan at lite.net</A>
  64 // Software Engineer : www.lite.net
  65 // Personal WWW      : www.jdg.net
  66 // IRC - (extasy)    : irc.lite.net
  67 -----------------------------------------
  68
  69 |<i>3. SQL DataBase Support for IRC Services:
  70 </I>|<i>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  71 </I>|<i>WOOOHOOO!! YEAH! :)
  72 </I>|<i>
  73 </I>|<i>Just think of the possibilities here?  Web sites which enables users to
  74 </I>|<i>send
  75 </I>|<i>and receive memo's.  Nice HTML pages for nickserv and chanserv access
  76 </I>|<i>lists?
  77 </I>|<i>
  78 </I>|<i>Cewl nick browsers for registered nicks?  Nickname searches?  Nickname
  79 </I>|<i>PROFILES (You can even add pictures to the nicknames on an html interface
  80 </I>|<i>if
  81 </I>|<i>you know your php3 programming)
  82 </I>|<i>
  83 </I>|<i>History of nicknames?  This might include history on the nick's abusive
  84 </I>|<i>maners,
  85 </I>|<i>records of every account where the nickname has been suspended, or klined?
  86 </I>|<i>
  87 </I>|<i>I am really not going to say more here...   Be creative, and think it out
  88 </I>|<i>for
  89 </I>|<i>yourselve, this is key!!!
  90 </I>|<i>
  91 </I>|<i>For compatibility reasons, I would make the suggestion that the SQL
  92 </I>|<i>DataBase
  93 </I>|<i>be made an additional extra, or DEFINATELY enable / disable it with config
  94 </I>|<i>or Makefile options.  I would actually recommend to enable / disable this
  95 </I>|<i>in
  96 </I>|<i>the Makefile, because of the fact that database support for the services
  97 </I>|<i>can
  98 </I>|<i>make the binaries rather big.
  99 </I>|<i>
 100 </I>|<i>Not everyone will have access to SQL databases, so we can't make Services
 101 </I>|<i>depend on this type of database. But the advantages is obviously quite a
 102 </I>|<i>bit...
 103 </I>
 104
 105 ---------------------------------------------------------------
 106 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
 107 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
 108
 109
 110 </PRE>
 111
 112 <!--endarticle-->
 113     <HR>
 114     <P><UL>
 115         <!--threads-->
 116         <LI>Previous message: <A HREF="000548.html">[IRCServices] combining services databases
 117 </A></li>
 118         <LI>Next message: <A HREF="000553.html">[IRCServices] New services implementations &amp; Updates?
 119 </A></li>
 120          <LI> <B>Messages sorted by:</B>
 121               <a href="date.html#551">[ date ]</a>
 122               <a href="thread.html#551">[ thread ]</a>
 123               <a href="subject.html#551">[ subject ]</a>
 124               <a href="author.html#551">[ author ]</a>
 125          </LI>
 126        </UL>
 127
 128 </body></html>