From kolab-format Mon Jan 05 10:39:30 2009 From: Martin Konold Date: Mon, 05 Jan 2009 10:39:30 +0000 To: kolab-format Subject: Re: [Kolab-devel] Horde can now store Preferences in IMAP (was: Horde Message-Id: <200901051139.31696.martin.konold () erfrakon ! de> X-MARC-Message: https://marc.info/?l=kolab-format&m=123115245119917 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0711309600==" --===============0711309600== Content-Type: multipart/alternative; boundary="Boundary-00=_jNeYJFuR5JbqDfU" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-00=_jNeYJFuR5JbqDfU Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Am Montag, 5. Januar 2009 10:19:55 schrieb Bernhard Reiter: Hi Bernhard, > This is what makes the discussion interesting. The use of LDAP for > daily client preferences in Kolab Server 2.2.0 was by mistake. No it was an intermediate solution in order to avoid an additional piece of= =20 compley software (RDBMS). > Until we have a good proposal for the Kolab Format, it should be file, > as this is what most other clients also use. Using a file instead of IMAP breaks the scalability aspect of the Kolab=20 Webclient.=20 > A client could potentially write this data on any display refresh > or client action. Just think about index files that contain special flags > per email. So I guess that there will be always client data that will need > to be saved client locally per user. I don't understand this. E.g. a webclient can easily use the more efficient= =20 session instead of persistent storage in order to keep volatile data (which= =20 can easily be regenerated anyway) Regards, =2D- martin =2D-=20 e r f r a k o n Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker Sitz: Adolfstra=DFe 23, 70469 Stuttgart, Partnerschaftsregister Stuttgart P= R 126 http://www.erfrakon.com/ --Boundary-00=_jNeYJFuR5JbqDfU Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable

Am Montag, = 5. Januar 2009 10:19:55 schrieb Bernhard Reiter:

Hi Bernhard= ,

> This i= s what makes the discussion interesting. The use of LDAP for

> daily = client preferences in Kolab Server 2.2.0 was by mistake.

No it was a= n intermediate solution in order to avoid an additional piece of compley so= ftware (RDBMS).

> Until = we have a good proposal for the Kolab Format, it should be file,

> as thi= s is what most other clients also use.

Using a fil= e instead of IMAP breaks the scalability aspect of the Kolab Webclient.

> A clie= nt could potentially write this data on any display refresh

> or cli= ent action. Just think about index files that contain special flags

> per em= ail. So I guess that there will be always client data that will need

> to be = saved client locally per user.

I don't und= erstand this. E.g. a webclient can easily use the more efficient session in= stead of persistent storage in order to keep volatile data (which can easil= y be regenerated anyway)

Regards,

-- martin

--

e r f r a k= o n

Erlewein, F= rank, Konold & Partner - Beratende Ingenieure und Physiker

Sitz: Adolf= stra=DFe 23, 70469 Stuttgart, Partnerschaftsregister Stuttgart PR 126

http://www.= erfrakon.com/

--Boundary-00=_jNeYJFuR5JbqDfU-- --===============0711309600== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kolab-format mailing list Kolab-format@kolab.org https://kolab.org/mailman/listinfo/kolab-format --===============0711309600==--