-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Krzeminski, Damian (BL60:9D30) Sent: Friday, October 30, 2009 3:59 PM To: [email protected] Subject: Re: [sipX-dev] Options for XMPP Profile/Avatar synchronization
Xingjun Chu wrote: > 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. > What about synchronizing through REST /my/contact-information service? [Chu, Xingjun [CAR:9D10:EXCH]] Sorry, I didn't make it clear. Absolutely, that is what I am going to use as interface to sipX in the plug in. I responded to your question here: http://permalink.gmane.org/gmane.comp.voip.sipx.devel/18947 If you don't get what you need from existing REST services please tell us and we'll improve them or implement something new. D. _______________________________________________ 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/
