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

List:       kolab-devel
Subject:    Re: [Kolab-devel] Completing ActiveSync integration in Kolab,
From:       Bernhard Reiter <bernhard () intevation ! de>
Date:       2010-03-22 16:37:42
Message-ID: 201003221737.42990.bernhard () intevation ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Montag, 22. März 2010 13:34:43 schrieb Georg C. F. Greve:
> On Monday 22 March 2010 13:15:22 Bernhard Reiter wrote:
> > While the protocol is activesync, I wonder if using a more generic name
> > would be have an advantage.
>
> Other protocols would likely want to store different metadata, or at least
> in different format. Since we would then be in a namespace conflict, this
> seemed like the right abstraction level.

Currently you are looking at creating an annotation to indicate
which folder is relevant for mobile sync for which device.
Given that serial number just is a unique number, this looks universal to me.

Note that clients would also need to support reading and setting this 
annotation. Overall I think we should also bring this discussion to 
kolab-format@.

Just out of curiosity: Where is the status of the sync saved in the z-push 
backend? Usually there will be a place for this in the connector itself.
I am asking because I think that should be a full cache, so if thrown 
completely away, the system should be self healing.

Bernhard


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

["signature.asc" (application/pgp-signature)]

_______________________________________________
Kolab-devel mailing list
Kolab-devel@kolab.org
https://kolab.org/mailman/listinfo/kolab-devel

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