From kmail-devel  Thu Jul 24 23:04:41 2003
From: Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date: Thu, 24 Jul 2003 23:04:41 +0000
To: kmail-devel
Subject: Re: CIA proposal (was: ClientInterface)
X-MARC-Message: https://marc.info/?l=kmail-devel&m=105908797612076
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============84889301646023174=="


--===============84889301646023174==
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_LYGI/Pd10o33Hcm";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--Boundary-02=_LYGI/Pd10o33Hcm
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 24 July 2003 16:15, Marc Mutz wrote:
> On Wednesday 23 July 2003 06:58, Don Sanders wrote:
> > 3) If this approach works then it does address the criticism of
> > having multiple clients modify index files but there's still the
> > memory costs associated with this approach. Each client will need
> > there own kmmsgdict, IIRC each entry in the kmmsgdict maps a
> > sernum -> (folder , index ) which is an int -> (int, int) mapping
> > or 12 bytes. I have >500K messages currently, so that's >6MB per
> > client instance.
>
> You typically won't run that many KMail instances that these few MB
> make any difference. Once a lib is split off of KMail for other apps
> to use, I don't think most other apps will have a great need for the
> dictionary.

I agree. Typically no user will have more than two KMail instances=20
running at the same time. The first instance will be the one that runs=20
on his workstation and the second instance will just be fired up to=20
check some messages while being away from the workstation. This second=20
instance will not be left running.

> > Besides folder files there are also other files than need to be
> > handled. The config file is a problem if it is desirable to have
> > each client keep their config dialogs and general configuration
> > info in sync.
>
> I'm cool with having that break. If a user is dumb enough to keep the
> config dialogs of two KMail's open at the same time, then he
> shouldn't complain if the second-to-be-closed one overwrites the
> settings of the first-to-be-closed one. I don't see a need to make
> that work.

I agree. I don't think that any KDE program (or any other application)=20
takes care of this.

Regards,
Ingo


--Boundary-02=_LYGI/Pd10o33Hcm
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc1 (GNU/Linux)

iD8DBQA/IGYLGnR+RTDgudgRAnv0AKCZ7o9ihXd4ZuvN4m4D5xm13F4uCQCguybu
390UUURAc+wnBkAKEduoOq8=
=zTcN
-----END PGP SIGNATURE-----

--Boundary-02=_LYGI/Pd10o33Hcm--

--===============84889301646023174==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

--===============84889301646023174==--