[Kolab-devel] Updated Kolab WebClient

[Adriaan Putter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Stuart Bingë wrote:

| When reading existing memos (i.e. those created by the Kolab KDE Client, etc)
| where the extension headers that we've added don't exist, we just use
| defaults for things like the memo category (eg. "Unfiled"). The Memo ID that
| mnemo uses seems to be a sequential integer, so all that we do when loading
| is read in the "valid" memos, then sequentially assign a new "memo id" to the
| invalid memos starting from the highest valid memo id that we read, plus one.

Surely the memo id is just a unique identifier and surely could be anything.
Can't you use something from the existing MIME headers that makes each memo
unique? If you look at the Turba driver, when I developed it I used the UID of
the message header as my Unique key.

Regards,
- --
Adriaan Putter
Code Fusion cc

GPG Key:
http://www.mandrakesecure.net/cks/search.cgi?stype=keyid_4b&keyid_4b=8B90E6FD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6-2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAj9LGwYACgkQj20UkouQ5v0yFgCaAjg2I41bXLD4N/7C2b6V1BCI
wsEAoKbVmm2NY0uK6Tudv8echp0KrFt6
=Br9d
-----END PGP SIGNATURE-----