[cvs] [Wiki] changed: Project/ActiveSync

[Michael Rubinsky]

mrubinsk  Fri, 26 Mar 2010 18:34:17 -0400

Modified page: http://wiki.horde.org/Project/ActiveSync
New Revision:  1.18
Change log:  Basic device setup, and some notes about iPhone

@@ -42,8 +42,16 @@
  || Android SDK Emulator|| 2.0.1 and 2.1 ||Contacts only as the  
emulator does not have a native calendar application ||
  || Motorola Droid || Android 2.0.1 || Contacts and Calendar data  
(Native calendar still has some issues) ||
  || !TouchDown For Droid || Version 5.1.0028 || Contacts and Calendar ||
  || iPod Touch || 3.1.3 || Contacts and Calendar ||
+
++++ Setting up the device
+
+It's beyond the scope of this page to go into detail for each  
individual device. In general, you will need to create a new account  
on your device. The account type should be something like //Microsoft  
Exchange// or //!ActiveSync//. Some devices use //Corporate//. You  
will need to enter your normal Horde username and password in the  
appropriate fields. In the field for the server address, you should  
enter the **root** of the webserver or virtual host that hosts Horde.  
For example, if you host horde at http://host.example.com/horde then  
you should enter http://host.example.com. You can ignore any reference  
to a //domain// entry.
+
+A special note for the iPhone/iPod (and possibly others) - if you do  
not use a SSL enabled site you may receive errors about not being able  
to find the !ActiveSync server. If this happens, just continue, or  
save, or whatever your option is to continue.  On the iPhone, after  
everything is completely set up, you must go back into the account  
settings and disable SSL.
+
+After the connection particulars are entered, you should choose to  
enable the folders that you want sync'd. Right now only Contacts and  
Calendar are supported.

  ++ 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.