Hi,
Did some research, I found that the user profile could be synchronized
between sipX and openfire (xmpp server) via the following options.
1) Open fire stores user profile in postgres database on sipX.
Synchronization could be done at database level. Basically user
profile could be pulled from sipXconfig into database which behaves like
a big cache.
It could be done by some external tool.
2) Openfire presents those user profile through XMPP vcard format
(XEP-0054: vcard-temp) to xmpp client such as pidgin. Base on this fact,
an openfire plug in could be created to register a new so called "VCard
provider". By default openfire interacts with a default Vcard provider,
i.e. the database to load/create/delete/update user profile/vcard info.
We could use a plug in to create a Vcard provider which instead of
access database, it talks to sipX to query/update the profile based on
the username. For users not existing in sipX world, the new provider
could query/update the default provider to get the profile info.
Notes: In Openfire, Avatar also is part of Vcard info which will be
treated the same way as other field. The only thing is the avatar has to
be based64 encoded.
The first option's main disadvantage is that it duplicates info and need
extra efforts to maintain the consistency.
So Personally I am kind of leaning toward option 2.
Comments and any alternatives are welcome.
Thanks
Jason
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Campbell,
Alfred (BL60:9D30)
Sent: Monday, October 26, 2009 9:35 PM
To: [email protected]
Subject: [sipX-dev] XMPP Profile/Avatar synchronization
After some discussion in Jira (XX-6822) on XMPP client profile and
avatar synchronization several questions have come up in my mind.
Basically the whole idea is that when you login via an XMPP client your
contacts would have all relevant contact and avatar information
available via XMPP. The requirement we discussed was could the phonebook
and XMPP contact/avatar information be synchronized in some manner so
that the sipXconfig phonebook could be the single source for the
information.
After thinking about this a little some thoughts:
1. The avatar synchronization for me seems to be a higher priority
issue. Reason being is that clients like Pidgin display the avatar
prominently and it's a very nice visible way for you to identify
buddies/contacts.
2. The contact/phonebook information synchronization doesn't seem
useful. At least on Pidgin this information is not available in a
manner that makes this data overly useful.
3. Bria client doesn't use server side Avatar or XMPP vcard for contact
information.
4. Pidgin does use XMPP vcard for contact and avatar.
5. Bria client will be able to get contacts via phonebook with patch
(XX-6772).
Proposal from comments/facts above:
1. Get patch (XX-6772) reviewed and included to get Bria a consistent
server side phonebook.
2. Close issue (XX-6822) as editing phonebooks from client isn't
desired.
3. Open a new issue on Avatar synchronization and treat this as next
work item after XX-6772 inclusion.
4. Open another new issue for contact/phonebook synchronization if
someone can articulate the value a little more. Is there another XMPP
client that uses the contact information in a manner that makes it
useful?
Comments welcome.
Al
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
