DesignBuddyList » History » Version 12
Adrian Georgescu, 07/13/2009 05:24 PM
1 | 2 | Adrian Georgescu | = Buddy list = |
---|---|---|---|
2 | |||
3 | [[TOC(Design*, depth=1)]] |
||
4 | 1 | Adrian Georgescu | |
5 | * Account |
||
6 | * Address-book |
||
7 | * Buddy list |
||
8 | * Watcher list |
||
9 | * Presence rules |
||
10 | |||
11 | 3 | Adrian Georgescu | [[Image(sipsimple-buddy-list-design.png,width=600)]] |
12 | 1 | Adrian Georgescu | == Account == |
13 | |||
14 | * GET XCAP documents xcap-caps, pres-rules, resource-lists, pidf-manipulation, rls-services |
||
15 | * Sends Publish for event presence |
||
16 | * Maintains a '''Presentity''' attributed that is sent as body to Publish |
||
17 | * Sends Subscribe for event presence.info |
||
18 | * Sends Subscribe for event presence with Supported=eventlist |
||
19 | |||
20 | == Buddy lists == |
||
21 | |||
22 | 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. |
||
23 | |||
24 | 12 | Adrian Georgescu | * The buddy list is stored in the main resource-lists XCAP document '''index''' . |
25 | * If '''account.presence.subscribe_rls_services''' is true, a RLS document that contains a list of discrete SIP URIs we subscribe to is PUT on the server under SIP URI account-buddies@domain. Then a Subscribe is sent with Supported: eventlist for this SIP URI. |
||
26 | |||
27 | 1 | Adrian Georgescu | == Watcher lists == |
28 | |||
29 | Built based on the body of NOTIFY for event=presence.winfo. |
||
30 | |||
31 | == Presence rules == |
||
32 | |||
33 | Based on NOTIFY for event watcher.info we update the policy and PUT pres-rules document on the XCAP server. |
||
34 | 12 | Adrian Georgescu | |
35 | == Dialog rules == |
||
36 | |||
37 | Based on NOTIFY for event dialog.info we update the policy and PUT dialog-rules document on the XCAP server. |
||
38 | 4 | Adrian Georgescu | |
39 | 10 | Adrian Georgescu | == Icon exhange flow == |
40 | 4 | Adrian Georgescu | |
41 | 11 | Adrian Georgescu | Support in OpenXCAP server is necessary, see http://openxcap.org/ticket/100 |
42 | |||
43 | 9 | Adrian Georgescu | Publishing end-point, on change: |
44 | 1 | Adrian Georgescu | |
45 | 9 | Adrian Georgescu | 1. Generate a random filename: XYZ |
46 | 1. Build URL http://xcap.example.com/xcap-root/icon/users/sip:alice@example.com/XYZ.png |
||
47 | 1. HTTP PUT to xcap server |
||
48 | 1. Update <icon> element of pidf and PUBLISH new pidf |
||
49 | 1. HTTP GET for xcap-directory and locate previously uploaded icons |
||
50 | 1. HTTP DELETE any previous icon files |
||
51 | 1 | Adrian Georgescu | |
52 | 9 | Adrian Georgescu | On reboot: |
53 | 1 | Adrian Georgescu | |
54 | 9 | Adrian Georgescu | 1. HTTP GET for xcap-directory and locate previously uploaded icon (e.g. XYZ) |
55 | 1. HTTP GET http://xcap.example.com/xcap-root/icon/users/sip:alice@example.com/XYZ.png |
||
56 | 1 | Adrian Georgescu | |
57 | 9 | Adrian Georgescu | Subscribing end-point: |
58 | |||
59 | 1. Parse <icon> element of pidf received in Notify |
||
60 | 2. HTTP GET http://xcap.example.com/xcap-root/icon/users/sip:alice@example.com/XYZ.png |
||
61 | 3. Cache picture and check periodically |