software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000843.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="000840.html">
  11    <LINK REL="Next"  HREF="000844.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 10:05:45 PDT 2000</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000840.html">[IRCServices] cheers. ideas.
  22 </A></li>
  23         <LI>Next message: <A HREF="000844.html">[IRCServices] cheers. ideas.
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#843">[ date ]</a>
  27               <a href="thread.html#843">[ thread ]</a>
  28               <a href="subject.html#843">[ subject ]</a>
  29               <a href="author.html#843">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>well, the &quot;Read on, write many&quot; method for large data exchange is really
  35 obsolete, YES, it is needed
  36 a lot of developement, skills and time, but nothing grows without effort and
  37 dedication.
  38
  39 the box that runs the brasnet services, have 256mb ram and 766mb of swap..
  40 the old configuration was 256mb swap, and when this limit is reached the
  41 services die.. and everyone knows, &quot;swap sucks&quot; ehhe, but its needed, i dont
  42 have money for 1gb ram. lol.. :)
  43
  44 &gt;<i> What we should focus on is writing an interface for Services that allows
  45 </I>&gt;<i> external apps to communicate with it.
  46 </I>
  47 a Library! it is a good way to retrieve information.. pre-built funcions..
  48 for listing information about nicks and chans.. memos. well..
  49 but.. write data to the database is a difficult thing to do.. &quot;read once..&quot;
  50 stuff.
  51 i can help writing a lib too, however preferring database storage, but,
  52 alone i dont do anything.
  53
  54 sorry about my english, im brazialian :)
  55
  56 Cheers,
  57 Bruno Lacerda
  58 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">sniffer at sniffer.net</A>
  59 <A HREF="http://sniffer.net">http://sniffer.net</A>
  60
  61
  62 ----- Original Message -----
  63 From: &quot;Andrew Kempe&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">andrewk at icon.co.za</A>&gt;
  64 To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at Snow.shadowfire.org</A>&gt;
  65 Sent: Wednesday, October 11, 2000 12:44 PM
  66 Subject: Re: [IRCServices] cheers. ideas.
  67
  68
  69 &gt;<i> Services is a READ ONCE, WRITE MANY application. If you make changes to
  70 </I>the
  71 &gt;<i> data in the underlying datastore, be it a database, binary file or text
  72 </I>&gt;<i> file, the changes would be lost at the next database save.
  73 </I>&gt;<i>
  74 </I>&gt;<i> Services would require a lot of work to make it support proper querying of
  75 </I>a
  76 &gt;<i> database. The performance hit services would take would outweigh the
  77 </I>benefit
  78 &gt;<i> imho. If one were to do it properly, with multiple threads loading only
  79 </I>the
  80 &gt;<i> information needed to service the users and channels currently online,
  81 </I>&gt;<i> things would definately be better. However, let's be honest, this requires
  82 </I>a
  83 &gt;<i> lot of developement, skills and time.
  84 </I>&gt;<i>
  85 </I>&gt;<i> What we should focus on is writing an interface for Services that allows
  86 </I>&gt;<i> external apps to communicate with it.
  87 </I>&gt;<i>
  88 </I>&gt;<i> Back to your point about Brasnet, 98MB is a lot. However, it's not totally
  89 </I>&gt;<i> unreasonable. The thing I'd guess that is really taking a hit is the CPU.
  90 </I>&gt;<i> The algorithms were never meant to handle so much data. I am definately
  91 </I>&gt;<i> looking to improve the key ones.
  92 </I>&gt;<i>
  93 </I>&gt;<i> Andrew
  94 </I>
  95
  96
  97 ---------------------------------------------------------------
  98 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
  99 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
 100
 101
 102 </PRE>
 103
 104 <!--endarticle-->
 105     <HR>
 106     <P><UL>
 107         <!--threads-->
 108         <LI>Previous message: <A HREF="000840.html">[IRCServices] cheers. ideas.
 109 </A></li>
 110         <LI>Next message: <A HREF="000844.html">[IRCServices] cheers. ideas.
 111 </A></li>
 112          <LI> <B>Messages sorted by:</B>
 113               <a href="date.html#843">[ date ]</a>
 114               <a href="thread.html#843">[ thread ]</a>
 115               <a href="subject.html#843">[ subject ]</a>
 116               <a href="author.html#843">[ author ]</a>
 117          </LI>
 118        </UL>
 119
 120 </body></html>