WebAPI/AppDefinedTeleophony: Difference between revisions

WebAPI/AppDefinedTeleophony (view source)

39 bytes added , 8 April 2013

Confirmed users

398

edits

Revision as of 15:21, 8 April 2013 (view source) Thinker (talk \| contribs) (→‎Communication Apps) ← Older edit		Revision as of 15:22, 8 April 2013 (view source) Thinker (talk \| contribs) (→‎Communication Apps) Newer edit →
Line 59:		Line 59:
	The communicaton apps are responsible for handling incoming calls and messages. But, they store contacts, messages, and call history in ContactsAPI, Messaging API, and call history API.		The communicaton apps are responsible for handling incoming calls and messages. But, they store contacts, messages, and call history in ContactsAPI, Messaging API, and call history API.

	Communication Apps should be registered with their capabilities, so a contacts app can provide correct functions to user for a given address handled by a communication App. That means we should provide an API to query capabilities of and list apps.		Communication Apps should be registered with their capabilities; messaging, voice call, and video call, so a contacts app can provide correct functions to user for a given address handled by a communication App. That means we should provide an API to query capabilities of and list apps.