[IRCServices] cheers. ideas.

[&quot]

Services would mark structures  (nicknames, channels etc) as "changed". Only
those structures would be saved at each database save. Each save would take
place to a new file. A cron would then run to combine those files into a
single file. Obviously they'd be combined in the order they were saved to
preserve changes.

The benefits would be that only "changed" structures would need to be saved.
This would save time on networks with huge databases.

Considering the overhead of XML's metadata, as Andy pointed out, something
like this would be essential if the databases were saved using XML.

Andrew

> -----Original Message-----
> From: owner-ircservices at Snow.shadowfire.org
> [mailto:owner-ircservices at Snow.shadowfire.org]On Behalf Of Chris Knipe
> Sent: 14 October 2000 22:16
> To: ircservices at Snow.shadowfire.org; ircservices at Snow.shadowfire.org
> Subject: Re: [IRCServices] cheers. ideas.
>
>
> Hi again :)
>
> Andew,   Text/XML...  Once again I ask. What reference will
> services have to
> KNOW immediately WHERE it is supposed to update its information?  If you
> have 5000 nicks registered, are you expecting services to hunt
> through 5000
> text files to locate the right one, and then still expect services to be
> fast?
>
> Just my thought.
>
> ---
> Regards,
> Chris Knipe
> Cell: (083) 430-8151
>
> ----- Original Message -----
> From: Andrew Kempe <andrewk at icon.co.za>
> To: <ircservices at Snow.shadowfire.org>
> Sent: Wednesday, October 11, 2000 12:00 PM
> Subject: Re: [IRCServices] cheers. ideas.
>
>
> > This is the ideal situation...
> >
> > However, those who have worked with developing software that can handle
> > "modules" will probably know that it is not something one does in one
> Sunday
> > afternoon.
> >
> > On this note, I've considered moving the databases to a text
> based format
> > using XML. Because the databases are pretty much "read-only"
> (all changes
> > HAVE to be made via Services itself) this would allow for a pretty wide
> > range of applications to use them.
> >
> > I'm busy writing a test program that I'm going to want as many people to
> > test as possible to ensure that the XML lib that I'm using is going to
> work
> > everywhere. This is because the current database format will be replaced
> by
> > the new one.
> >
> > Are there any thoughts or concerns on using XML/text to store the
> > information?
> >
> > Andrew
> >
> > ----- Original Message -----
> > From: "Samuel Graenacher" <sam at breakfree.com>
> > To: <ircservices at Snow.shadowfire.org>
> > Sent: Wednesday, October 11, 2000 11:09 AM
> > Subject: Re: [IRCServices] cheers. ideas.
> >
> >
> > >
> > > Hmm, I dunno how fast/effective the current db format is but it sounds
> > like
> > > a good idea. Would allow easier data/user management with other
> software.
> > > Maybe make the database functions modular and let the user
> decide which
> db
> > > format to use?
> > >
> > > Andrew Kempe writes:
> > >
> > > > this bounced...
> > > >
> > > > > From: "Bruno Lacerda" <sniffer at sniffer.net>
> > > > > To: <ircservices at Snow.shadowfire.org>
> > > > > Subject: cheers. ideas.
> > > > > Date: Tue, 10 Oct 2000 19:37:44 -0300
> > > > >
> > > > > im a ansi c/database programmer, im currently working
> with webdevel
> > but
> > > > just
> > > > > for money.
> > > > >
> > > > > well, im completely open for help with new ways of
> storing,retrieving
> > > > > services information, such as databases..
> > > > >
> > > > > i dont know about the ircservices devel state, but, i
> suggest using
> > real
> > > > sql
> > > > > based databases.. mysql, postgres.. dunno.
> > > > >
> > > > > uh, a question, am i subscribed to the right mailing list?
> > > > >
> > > > > cheers, bruno lacerda.
> > > > > <A  HREF="http://sniffer.net">http://sniffer.net</A>
> > > > > sniffer at sniffer.net
> > > > >
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------
> > > > To unsubscribe, send email to majordomo at ender.shadowfire.org
> > > > with "unsubscribe ircservices" in the body, without the quotes.
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------
> > > To unsubscribe, send email to majordomo at ender.shadowfire.org
> > > with "unsubscribe ircservices" in the body, without the quotes.
> > >
> >
> >
> > ---------------------------------------------------------------
> > To unsubscribe, send email to majordomo at ender.shadowfire.org
> > with "unsubscribe ircservices" in the body, without the quotes.
>
>
> ---------------------------------------------------------------
> To unsubscribe, send email to majordomo at ender.shadowfire.org
> with "unsubscribe ircservices" in the body, without the quotes.
>


---------------------------------------------------------------
To unsubscribe, send email to majordomo at ender.shadowfire.org
with "unsubscribe ircservices" in the body, without the quotes.