[cvs] [Wiki] changed: Project/ActiveSync

[Michael Rubinsky]

mrubinsk  Fri, 26 Mar 2010 16:05:04 -0400

Modified page: http://wiki.horde.org/Project/ActiveSync
New Revision:  1.15
Change log:  tweaks, add some todos

@@ -45,23 +45,24 @@
  || iPod Touch || 3.1.3 || Contacts and Calendar ||

  ++ Rough list of issues/todos/development notes in no particular order

-Horde_History state driver. Currently, ActiveSync support uses a  
file-based state driver to persist the PIM state so we know what  
changes. This is a refactored implementation of what the Z-Push  
library does. For Horde, this is inefficient, as we have the data  
needed to know what has changed and when. Once the majority of the  
feature set is working, a Horde_History driver should be written to  
replace the file based driver when syncing contacts, calendar, and  
todo data. We might still need it if/when push email is implemented.  
The backend drivers are able to specify a particular state storage to  
enable this functionality if it is needed.
+Horde_History state driver. Currently, !ActiveSync support uses a  
file-based state driver to persist the PIM state so we know what  
changes. This is a refactored implementation of what the Z-Push  
library does. For Horde, this is inefficient, as we have the data  
needed to know what has changed and when. Once the majority of the  
feature set is working, a Horde_History driver should be written to  
replace the file based driver when syncing contacts, calendar, and  
todo data. We might still need it if/when push email is implemented.  
The backend drivers are able to specify a particular state storage to  
enable this functionality if it is needed.

-Need to implement ghosted properties / SUPPORTED tag. Currently, all  
data for a message on the server is overwritten and replaced with only  
what the PIM sends. It's possible for some PIMS to ghost contact and  
calendar properties so that only the supplied tags are changed, and  
missing, ghosted properties are retained on the server.  When a PIM  
supports this, it sends a SUPPORTED tag with children representing the  
NON-ghosted properties. The absence of the SUPPORTED tag would  
indicate that any property not transmitted should be handled as a  
ghosted property.
+Need to implement ghosted properties / SUPPORTED tag. Currently, each  
message that is sent from PIM -> Server is overwritten and replaced  
with only what the PIM sends. It's possible for some PIMS to ghost  
contact and calendar properties so that only the supplied tags are  
changed and missing, ghosted, properties are retained on the server.   
When a PIM supports this, it sends a SUPPORTED tag with children  
representing the NON-ghosted properties. The absence of the SUPPORTED  
tag would indicate that any property not transmitted should be handled  
as a ghosted property.

  Configurable heartbeat interval range: The protocol allows for  
rejecting heartbeat intervals that fall outside a specific range, and  
send back a suggested heartbeat interval to the client. This should be  
implemented as a configuration value.
+
+Support for provisioning is already implemented, but we still need to  
figure out all the possible policies available, and the values to use  
to set them etc... Once more are available, they should be added as  
configuration parameters.
+
+Todo syncing: Neither the iPod/iPhone or Android have a native Todo  
application. TouchDown does provide one, but backend support still  
needs to be added.

  ++ Resources

  http://z-push.sourceforge.net
  https://zimbrabackend.svn.sourceforge.net/svnroot/zimbrabackend/zimbra.php
  Some discussion/issues/info on calendar sycing
  http://z-push.sourceforge.net/phpbb/viewtopic.php?f=4&t=119&start=10
-
-Some work towards a Horde adapter for Z-Push:
-http://z-push.sourceforge.net/phpbb/viewtopic.php?f=4&t=879

  Some discussion on remote wipe issues with various devices
  http://z-push.sourceforge.net/phpbb/viewtopic.php?f=4&t=802

@@ -70,9 +71,9 @@

  Web-based client test
  https://www.testexchangeconnectivity.com/

-Another AS implementation in PHP, though we can't use it due to the  
license, there is some good information there for the taking.
+Another AS implementation in PHP - there is some good implementation  
information there for the taking.
  https://svn.tine20.org/svn/trunk/tine20/ActiveSync

  ----
  Back to the ((Projects|Project List))