[cvs] [Wiki] changed: Project/ActiveSync

[Michael Rubinsky]

mrubinsk  Sat, 24 Apr 2010 13:27:52 -0400

Modified page: http://wiki.horde.org/Project/ActiveSync
New Revision:  1.49
Change log:  this is moot now that we have a history driver

@@ -54,9 +54,9 @@
  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.
+After the connection particulars are entered, you should choose to  
enable the folders that you want sync'd. Contacts, Calendar and Tasks  
are supported, but your device also needs to support the requested  
folders.

  +++ Provisioning/!RemoteWipe

  Provisioning allows devices to be more tightly registered with a  
particular server. It enables the server to be able to send policy  
settings to the device. These policy settings include things like  
requiring a PIN to unlock the device, the complexity of the PIN  
required, the number of failed login attempts allowed etc...  
Additionally, it enables devices to be remotely wiped so that if a  
device is lost or stolen, the user or administrator can request the  
device to be wiped.
@@ -69,10 +69,8 @@

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

  * Implement more recent protocol version support - version 12 or  
maybe 12.1 (Exchange 2007??) should be fairly non-disruptive. Version  
12 would get us more atomic policy settings, local wipe rules, as well  
as the ability to send the policy settings to the client as the more  
compact wbxml. 14 (Exchange 2010?) would probably be lots more work as  
it does away with PING, using SYNC for waiting for changes instead.
-
-* Rework the PING command's use of state so that it only has to stat  
the messages that fall within the time period prescribed by the  
FILTERTYPE tag passed when SYNCing calendar folders.  Currently, the  
file driver is very wasteful in this regard, it has to stat **every**  
appointment message on the server since it knows nothing about the  
FILTERTYPE last used. Need to add the last used filtertype to the  
device's state file and use that in PING to set an appropriate filter  
type value for the state machine to use when diffing. This should  
improve performance greatly on calendars with a substantial amount of  
old events. Of course, this won't be an issue with a horde history  
driver.

  * Add configuration in Horde to allow specifying a specific  
addressbook to act like an Exchange GAL for !ActiveSync purposes.

  ++ What to do if you have problems (or How to help us debug your issue)