History

« Previous - Version 5/115 (diff) - Next » - Current version
Adrian Georgescu, 07/09/2009 02:28 pm

= Buddy list =

<acronym title="Design*, depth=1">TOC</acronym>

  • Account
  • Address-book
  • Buddy list
  • Watcher list
  • Presence rules

Image(sipsimple-buddy-list-design.png,width=600)
Account

  • GET XCAP documents xcap-caps, pres-rules, resource-lists, pidf-manipulation, rls-services
  • Sends Publish for event presence
  • Maintains a '''Presentity''' attributed that is sent as body to Publish
  • Sends Subscribe for event presence.info
  • Sends Subscribe for event presence with Supported=eventlist
Buddy lists

Contains list of buddies. The buddylist is indexed by SIP URIs. Additional one can store full name or other attributes. Based on NOTIFY for event=presence each buddy has a '''Presentity''' attribute that contains published information. GUI displays parts of it.

Buddy list is stored in resource-lists XCAP document. If RLS is used, a RLS document that can contains a list of discrete SIP URIs is built and PUT on the server.

Watcher lists

Built based on the body of NOTIFY for event=presence.winfo.

Presence rules

Based on NOTIFY for event watcher.info we update the policy and PUT pres-rules document on the XCAP server.

Icon storage

http://xcap.example.com/xcap-root/icon/users/sip:alice@example.com/icon.png

Public access: Anyone can do GET without being challenged with401.

Write access: PUT is 401-ed, only the owner can write it.

contact-details.jpg (45.6 kB) Adrian Georgescu, 02/01/2010 12:56 am

BuddyList-Aggregation.png (109.4 kB) Adrian Georgescu, 02/01/2010 01:16 am

PresencePolicy.png (38.8 kB) Adrian Georgescu, 02/12/2010 10:26 am