From kde-pim  Wed Feb 18 09:58:24 2015
From: Daniel =?ISO-8859-1?Q?Vr=E1til?= <dvratil () redhat ! com>
Date: Wed, 18 Feb 2015 09:58:24 +0000
To: kde-pim
Subject: Re: [Kde-pim] Is there interest in a MS Exchange Active Sync Resource ?
Message-Id: <5153726.DXOyfoIcgA () thor>
X-MARC-Message: https://marc.info/?l=kde-pim&m=142425353003158
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============4525426595171482825=="


--===============4525426595171482825==
Content-Type: multipart/signed; boundary="nextPart1742580.LQzMp3uk9z"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart1742580.LQzMp3uk9z
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Tuesday, February 17, 2015 08:05:20 AM Martin Koller wrote:
> On Monday 16 February 2015 19:49:45 Martin Steigerwald wrote:
> > Martin, would it be possible with a little adaption to not delete t=
he
> > mails from the server? That way I could use it to download mails fr=
om
> > inbox in parallel to the IMAP access so whenever IMAP access is bro=
ke =E2=80=93
> > which it is quite often (and I attribute much to that to exchange, =
Akonadi
> > may just be a bit fragile on reconnecting from all the connection
> > dropouts) =E2=80=93 I can still have at least the mails in inbox lo=
cally.
>=20
> To not delete the mails is simple, but the problem is to know which m=
ails
> were already downloaded so that I would not download them again and a=
gain.
>=20
> I'd need to check how to do that ...

According to specs each Collection in the Sync response should include =
a=20
SyncKey element. If you store value of the SyncKey element in an Akonad=
i's=20
Collection attribute (or you can use Akonadi::Collection::remoteRevisio=
n -=20
that what's the property is for actually), on next sync you then pass t=
he=20
stored SyncKey to the server and you should be given only new messages =
in=20
response + a new value of the SyncKey to store in the Collection. This =
is=20
similar to what we do in the Google Calendar resource for example.

Cheers,
Dan


=2D-=20
Daniel Vr=C3=A1til | dvratil@redhat.com | dvratil on #kde-devel, #konta=
ct, #akonadi
Software Engineer - KDE Desktop Team, Red Hat Inc.

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
--nextPart1742580.LQzMp3uk9z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAABAgAGBQJU5GJCAAoJEMWdYU9vSuNIPekIAI0DZYU/DrNtZsGTk63jN7m4
elvoIQGLLmFHRjdFFRKrUsrb1H+vdPcZOkJQlp9pZyG1KYo+sxYVc2PaxwKhbLxT
JSzVpVwhpuwb3F6gMBcVhM6T5JoflSyn/+Y/ZPSoQt/2R9Zbw6v8tWVFNAjHW+HD
SgvbNfF/qvviT7Wt49TjxJdD5FXzcWn09oqQo+88Q5/ZCC0iwJo8rvX+7pbTlUEe
7I6yfbw1UIdAh/6cmi5yilkjVLPVWC1etsphMmZ2YAs6aSK8yaLR9IiDO1lH01Nc
w0C3aymd/mfntng3r7mP6DhAmI7HSDnRNY7sJvdohS/6yHAZvkhTaun1OJzhxbg=
=Io6a
-----END PGP SIGNATURE-----

--nextPart1742580.LQzMp3uk9z--


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

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============4525426595171482825==--