from... synch from that end both both ways - server tries to resolve conflicts both...Master - Named service wins in conflicts. Requests have this as the base type. Message from remote service identifying an entity by it's UID and optionally its recurrenceid. Responses have this as the base type. Message from remote service requesting new subscription. token Sent in initial startup request principal-href Principal requesting the subscription. synch-token Passed back for operations on the calendar exchange-user Userid for exchange exchange-encpw Encoded password for exchange Response to message from remote service requesting new subscription. Message from remote service unsubscribing. Response to message from remote service requesting unsubscription. (Re)initialize the service subscribe-url: callback url for notifications and subscribe requests token: random token for subscribe requests. If token is unchanged this is just a keep alive ping Respond to the ping token: sent in initial request status: OK Message to remote service requesting synchronization info. Response to message to remote service requesting synchronization info. Message to add a calendar item. Response to message to add an item. Message to fetch a calendar item. Response to message to fetch an item. Message to update a calendar item. Response to message to update an item.