\documentclass{article} \usepackage{ulem} \usepackage{graphicx} \usepackage{hyperref} \pagestyle{headings} \begin{document} \part{ActiveSync Feature Grid} ++++The following is a chart showing the out of the box feature set of Horde\_ActiveSync used in conjunction with the Horde Groupware stack compared to other groupware stacks supporting EAS. Feature & Horde 4/5 & Z-Push 1/2 & Tine 2.0 & Notes \\ \hline Efficient memory use via use of temporary streams. & Yes, for reading/writing the WBXML data and for reading/writing MIME parts from IMAP server. & Yes, for reading/writing the WBXML data. & No & \\ \hline Easily sync multiple collections at once. & Yes & No & Yes & \\ \hline Fully extensible and useable outside of the groupware stack & Yes & No & Yes & \\ \hline Support SOFTDELETE for keeping the client's database in sync with the client selected date filters. & H5 & No & No & \\ \hline Choice of either SQL or NoSQL state storage. & Yes & No & No & As of Horde 5.2, the ActiveSync library supports storing state in MongoDB. \\ \hline Dynamic support for multiple folders per collection. & H5 & No & As of Horde 5.2, multiple folders are automatically synchronized when possible, or "multiplexed" together otherwise. & \\ \hline EAS 2.5 (Exchange 2003 SP2) & & & & \\ \hline Email sync & H5 - Using the efficient Horde\_Imap\_Client library. & Yes, using either Zarafa server or the "imap" backend which uses the built in php imap functions. & Yes & \\ \hline Email type property & H5 & No & No & This property provides clients the ability to display appropriate icons for the type of message. E.g., Meeting requests, MDN etc... \\ \hline Hierarchical folder support & H5 & & & \\ \hline Calendar sync & H4 & Yes, when syncing against Zarafa server. & Yes & \\ \hline Full meeting request/response & H5 & Yes, when syncing against Zarafa server. & No. & \\ \hline Tasks sync & H4 & Yes, when syncing against Zarafa server. & Yes & \\ \hline Contacts sync & H4 & Yes, when syncing against Zarafa server. & & \\ \hline GAL search & H4 & Yes, with a few backends. & Yes. & \\ \hline Provisioning/Remote Wipe & H4 - with improvements to security policy support in H5. & Yes, with exceptions for some devices and limited security policy support. & Yes, with limited security policy support. & \\ \hline EAS 12.0 (Exchange 2007) & & & & \\ \hline Autodiscover & H5* & * Major improvements to Autodiscovery in H5.1. & & \\ \hline HTML Email & H5 & & & \\ \hline Email search for items not synched to client & H5 & & & \\ \hline Email Flagging & H5 & & & \\ \hline Full MIME support & H5 & & & \\ \hline Set out of office message & H5 & & & \\ \hline EAS 12.1 (Exchange 2007 SP1) & & & & \\ \hline Reduced bandwidth features. & H5 & & & \\ \hline S/MIME on device encryption, decryption, and signing & H5 & & & \\ \hline EAS 14.0 (Exchange 2010 SP1) & & & & \\ \hline Notes Sync & H5.1 & & & \\ \hline SMS Sync & No & & & \\ \hline Conversation View & TODO & & & \\ \hline Reply state sync & H5.1 & & & \\ \hline Free/busy lookup & H5.1 & & & \\ \hline Nickname Cache & TODO & & & \\ \hline EAS 14.1 (Exchange 2010 SP2) & & & & \\ \hline Conversation Segments & TODO & & & \\ \hline GAL/Search Photos & H5.1 & & & \\ \hline Device Info & H5.1 & Device info can be used during provisioning process to allow finer control over device access/management. & & \\ \hline TODO: Security policies. & & & & \\ \hline
\end{document}