Archived:Source compatibility break in SIP APIs between S60 2nd Edition FP2/FP3 and S60 3rd Edition (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Compatibility

Platform(s): S60 2nd Edition and FP1, FP2, FP3
S60 3rd Edition (initial release)

---

Article

Created: User:Technical writer 1 (21 May 2007)

Last edited: hamishwillee (21 Jun 2012)

Description

The Session Initialisation Protocol (SIP) APIs introduce a source compatibility break in S60 2nd Edition FP2/FP3 and S60 3rd Edition.

In S60 2nd Edition, SIP is not part of the platform, but available as an add-on for S60 2nd Edition SDKs. In S60 3rd Edition, SIP APIs are integrated into the platform.
The source compatibility break introduces some complexity into developing SIP client applications with support for both S60 editions. In practice, developers need to choose between conditional compiling with platform-specific macros and maintaining two separate versions of the code.