How to implement activesync protocol in iphone application?

Question

How to implement activesync protocol in iphone application? Any advice, any documents and tutorials come well.

I read Exchange ActiveSync and iOS 4 Devices from apple. Are there any real documents for this?

Answer 1

It is difficult, but not impossible, to write an application that is exchanged using active exchange synchronization. The Jons answer Exchange Server Protocol link contains a document called MS-ASWBXML. You must write the encoder for wbxml yourself, and the document clearly describes the needs. In addition, I highly recommend this document: http://www.w3.org/TR/wbxml/

If the low level works, you need to implement the EAS protocol over ob wbxml, which is not trivial, due to errors in the documentation, different behavior of different versions of the protocol. There will be many trial errors to check why the exchange server does not understand your requests; -)

Answer 2

Despite asking the question in a comment, you can look for Microsoft documentation on Exchange Server protocols .

If you are thinking of introducing your own client, I would strongly advise you to pause and think whether it is really worth it. As someone who worked on server-side implementation of these protocols, I can say that they can become quite complex - and the documentation does not always give you enough information. (In some areas this is also wrong).

Answer 3

Using Apple's native support means using the Apple API to write to the address book and calendar storage on your phone. Your application should not know anything about how data is synchronized: it just happens in the background.

If you need direct control over the synchronization process, the Apple API will not be able to help you. Jon Skeet's answer contains a link to the documentation on the Microsoft protocol, but as he mentioned, you'll tune in to the world of pain.

Answer 4

EAS is really intended for device manufacturers to implement, not normal application development. You should look at the documentation for the ActiveSync protocol and study the protocol license (yes, this is a payment license), and then ask yourself whether it is worth writing all the business logic, coding logic, intensive testing and licensing. An alternative is to use Exchange Web Services (EWS), which may be much better suited - more rhobust in many areas and does not require licensing.

You should also look at this: http://blogs.msdn.com/b/webdav_101/archive/2011/09/29/new-to-exchange-activesync-development.aspx