[commits] [Wiki] changed: ActiveSync/Development

[Michael Rubinsky]

mrubinsk  Wed, 23 Nov 2016 15:42:43 +0000

Modified page: https://wiki.horde.org/ActiveSync/Development
New Revision:  3
Change log:  Make it clear this is in addition to the WBXML data.

@@ -46,9 +46,9 @@
  From here, we instantiate a //Horde_Rpc_ActiveSync// object and  
inject a //Horde_ActiveSync// object (which is created using  
//Horde_Core_Factory_ActiveSyncServer//).

  Here, we perform some sanity checking on the request and sniff out  
what type of request we are handling. OPTIONS and Autodiscover  
requests are handled a little differently, but for now we will  
concentrate on the "normal" request handling.

-The client must send certain data with each request. This data is  
either present as "normal" GET variables or is sent as BASE64 encoded  
binary data sent in QUERY_STRING (see  
//**Horde_ActiveSync::getGetVars()**//). The format of this binary  
data is beyond the scope of this page, but the data is decoded in  
//**Horde_ActiveSync_Utils::decodeBase64()**//.
+The client must send certain data, apart from the WBXML structure,  
with each request. This data is either present as "normal" GET  
variables or is sent as BASE64 encoded binary data sent in  
QUERY_STRING (see //**Horde_ActiveSync::getGetVars()**//). The format  
of this binary data is beyond the scope of this page, but the data is  
decoded in //**Horde_ActiveSync_Utils::decodeBase64()**//.

  : Cmd : This is the command or request type. E.g., SYNC, PING, FOLDESYNC
  : !DeviceId : This is a unique identifier for the client. This value  
is only unique to the client, not to the account. I.e., the same  
physical device/application will have the same !DeviceId. Multiple  
users can be associated with the same !DeviceId.