|
Explain SIMPLE (SIP for Instant Messaging and Presence leveraging Extensions)? michaeldavid23 11-July-2008 11:11:43 AMComments References: IETF RFC 2778 and 2779 Posted by george99 • In the group of protocols known as Instant Messaging and Presence (IMP) • “A presence and instant messaging [IMP] system allows users to subscribe to each other and be notified of changes in state, and for users to send each other short instant messages.” (IETF 2778) • Uses Subscribe and Notify SIP methods to update a database Terms • Presentity – Provides presence information to be stored and distributed • Watcher – receives information from the service • Fetcher – Requests current values from the Presentity • Poller – Special case of a fetcher, requests information on a regular basis • Subscriber – Requests notification of a future change in status (usually a UAC) Posted by yogendra In computing, SIMPLE (Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions) is an instant messaging (IM) and presence protocol suite based on Session Initiation Protocol (SIP). Like XMPP, and in contrast to the vast majority of IM and presence protocols used by software deployed today, SIMPLE is an open standard. Both are IETF standards or proposed standards. Posted by sagitraz |
Posted: 12-July-2008 04:06:40 AM By: sagitraz In computing, SIMPLE (Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions) is an instant messaging (IM) and presence protocol suite based on Session Initiation Protocol (SIP). Like XMPP, and in contrast to the vast majority of IM and presence protocols used by software deployed today, SIMPLE is an open standard. Both are IETF standards or proposed standards. | |
Posted: 14-July-2008 12:03:04 PM By: yogendra • In the group of protocols known as Instant Messaging and Presence (IMP) • “A presence and instant messaging [IMP] system allows users to subscribe to each other and be notified of changes in state, and for users to send each other short instant messages.” (IETF 2778) • Uses Subscribe and Notify SIP methods to update a database Terms • Presentity – Provides presence information to be stored and distributed • Watcher – receives information from the service • Fetcher – Requests current values from the Presentity • Poller – Special case of a fetcher, requests information on a regular basis • Subscriber – Requests notification of a future change in status (usually a UAC) | |
Posted: 14-July-2008 12:05:38 PM By: george99 References: IETF RFC 2778 and 2779 |