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

List:       kde-core-devel
Subject:    Re: [PATCH] KConfigBackend
From:       Hans Meine <hans_meine () gmx ! net>
Date:       2002-02-25 22:25:23
[Download RAW message or body]

Waldo Bastian <bastian@kde.org> writes:
> > b) i don't like the ksavefile vs. fopen code. i'm in favour of moving this
> >   whole discrimination to ksavefile (and obviously adding some more options
> >   to it).
> 
> That breaks the semantics of KSaveFile. In order for abort to work you must 
> create a new file.

What about (for KSaveFile)

1. creating the new file first and

2. in case of a not-owned orig file or non-stale symlink,

  a) try to "fill" the original with the contents of the new file
     preserving everything as far as possible

  b) if that does not work, goto 3. as it does now

3. else move the tempary file over the original as KSaveFile does now.

AFAICS, the only case of possible danger is when 2. is the case
(i.e. the new logics come into play), a) does destroy the data but
does not work but 3. also fails. I guess KSaveFile as it is now has
about the same "weakness": That 3. does destroy data but fails
anyways. I cannot imagine cases for any of both?

------------------------

BTW: I just saw the "Application Configuration Access Protocol" (ACAP)
mentioned in a mail on kde-look and did not want to spam kde-core,
however maybe you dare? I guess someone might have a think about it
(mentioned as a solution for sharing common KDE settings between
computers with different Home directories):

  http://asg.web.cmu.edu/acap/

Also, some days ago, someone mentioned the Netscape Roaming Profiles
which he/she liked, so maybe this is of interest?

-- 
Ciao,  /  /
      /--/
     /  / ANS                          .,* Hamburg, Germany *,.
[prev in list] [next in list] [prev in thread] [next in thread]