[Pidgin] #7990: Support XEP-0048 -- Bookmarks -- for storage of list of XMPP MUCs

[Pidgin]

#7990: Support XEP-0048 -- Bookmarks -- for storage of list of XMPP MUCs
--------------------------------+-------------------------------------------
 Reporter:  mcepl               |     Owner:  deryni
     Type:  enhancement         |    Status:  new   
Component:  XMPP                |   Version:  2.5.3 
 Keywords:  XEP-0048, XEP-0049  |  
--------------------------------+-------------------------------------------
 Specialized XMPP-only clients (at least I am sure it is true about psi and
 gajim; [http://wiki.kde.org/tiki-index.php?page=Kopete+Jabber+Muc there is
 even a rudimentary support in kopete]) are able to store the bookmarks
 marking XMPP MUCs on the server (with optional bit whether the MUC should
 be joined automatically on the connect to the account).

 XEP for this functionality is [http://xmpp.org/extensions/xep-0048.html
 XEP-0048] (many servers still use
 [http://xmpp.org/extensions/attic/xep-0048-1.0.html the old version] which
 is more simple) and store them according to
 [http://xmpp.org/extensions/xep-0049.html XEP-0049] (private storage), and
 in the future [http://xmpp.org/extensions/xep-0060.html XEP-0060] (PEP)
 should be used instead.

 Of course, there might be a problem with UI design for the multiprotocol
 client, where one kind of storage must be used for one protocol (assuming
 no other protocol is able of doing this) and other kind of storage for
 others. However, I believe that there shouldn't be that many
 synchronization problems, because if the availability of the private
 storage is indicate by the presence of 'jabber:iq:private' namespace, then
 pidgin should post all current non-duplicate bookmarks in the local
 storage to the remote storage and then remove it, and in the following use
 of the account use just XMPP Bookmarks.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/7990>
Pidgin <http://pidgin.im>
Pidgin