[commits] [Wiki] changed: ActiveSync

[Michael Rubinsky]

mrubinsk  Tue, 11 Jun 2013 14:24:55 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  197
Change log:  Update some feature differences now that both of these  
libraries have had improvements.

@@ -274,13 +274,14 @@

  # Modularity. Separate classes for maintaining device state and for  
obtaining message diffs. If not using Horde as a backend, all that is  
needed is to write a new class that extends  
Horde_ActiveSync_Driver_Base. This allows the backend, itself, to  
determine the best way to calculate diffs...like using Horde's History  
system. In Z-Push, diff generation and state management are tightly  
coupled.
  # Efficiency. The history based diff engine is orders of magnitude  
more efficient than Z-Push's file based diff backend.
  # Unless using Zarafa, Z-Push contained no message-specific logic.  
For example, no code for dealing with appointment related issues such  
as timezones, recurrence series etc. Horde_ActiveSync contains support  
for these things out of the box.
+# Horde's ActiveSync library supports a larger set of available EAS  
security policies.
  # At least at the time of writing, Horde allowed better  
configuration of things such as heartbeat/timeout intervals. We also  
actually allow configuring available security policies. Z-Push had  
basic support for provisioning and for turning on or off the  
requirement for a device PIN - but contained no facility for  
configuring any of the other options without editing code.  Also, if  
using Horde_ActiveSync as part of a typical Horde install you get all  
the ease of configuration that our administration interface provides.
  # I don't have hard data on device compatibility as it compares to  
Z-Push, but I do know that we have fixed some device specific issues  
in the past that - at least at the time of this writing - were not  
working with Z-Push. Certain Nokia devices come to mind that use !MfE.  
Z-Push lists these as "unknown" compatibility but they work, at least  
for contacts/calendar with Horde. Remote wiping iOS devices is also  
problematic in Z-Push.
  # Email sync with Horde_ActiveSync uses the vastly more efficient  
Horde_Imap_Client library and takes full advantage of IMAP servers  
with QRESYNC capabilities. Z-Push uses the very poor performing  
c-client PHP extension.
-# Horde's email support is more complete than Z-Push's IMAP based  
implementation - with support for version 12.0 style email store  
searching, follow-up flag synchronization, S/Mime signatures and  
encryption, and more.
-# Horde_ActiveSync currently supports almost the full feature set up  
to Exchange 2007sp1 - Z-Push has code in development that works to  
some extent with 2007 and plans to look at supporting up to 2010.
+# Horde's email support is more complete than Z-Push's IMAP based  
implementation - with support for version 12.0 style email store  
searching, follow-up flag synchronization, reply,forward history  
synchronization, S/Mime signatures and encryption, and more.
+# Horde_ActiveSync currently supports almost the full feature set up  
to Exchange 2010sp1 - Z-Push 2 works with Exchange 2007 has code in  
development that works to some extent with 2010.
  # Horde_ActiveSync supports multiple users per device - when the  
device supports it. AFAIK, Z-Push only supports a single user account  
per device.

  ++ Resources