[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Proposal: KSharedFile
From:       Nick Papadonis <npapadon () yahoo ! com>
Date:       2001-12-11 8:14:25
[Download RAW message or body]

Nick Papadonis <npapadon@yahoo.com> writes:

> On Friday 07 December 2001 19:52, Ingo Assenmacher wrote:
> >
> > But why do not use a database with transactions and
> > multiuser-evironment to solve concurrency issues here. Instead of
> > KsharedFile make something like KFileProxy and connect to a database.
> > Concurrent access to data including integrity issues have been solved
> > for many years now by database systems. So why keep up with fragile
> > file-based manipulations and lock-files?

Another value add:
        (accsess time large db) < (access time large multiple flat files) 

No?

- Nick



> 
> <nick>
> I have to agree with Ingo.  IMHO using some sort of database is the
> easiest and best solution for long term.  Database engines and libraries are freely
> available and already have most bugs ironed out.  I also believe 
> engineering hours are saved using a well known database opposed to
> developing new code to deal with a flat file for storage.
> 
> Just lock the database when a device is syncronizing, release the lock
> afterwards.
> 
> In response to debugging - If someone with database experience
> could come up with a schema and API for KPIM's needs, we shouldn't
> need to deal with this.  
> 
> </nick>
> 
> _______________________________________________
> kde-pim mailing list
> kde-pim@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kde-pim
> 

-- 
Nick
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
[prev in list] [next in list] [prev in thread] [next in thread]