[Pidgin] #2194: XMPP services access

[Pidgin]

#2194: XMPP services access
--------------------------+-------------------------------------------------
  Reporter:  vitb         |       Owner:       
      Type:  enhancement  |      Status:  new  
  Priority:  minor        |   Milestone:       
 Component:  libpurple    |     Version:  2.0.2
Resolution:               |    Keywords:       
   Pending:  0            |  
--------------------------+-------------------------------------------------
Comment (by zdenek):

 Just some more info about how the transports can be used:
 On our jabber server, I can use them for: ICQ, AIM, MSN, Yahoo, IRC, Gadu-
 Gadu, Tlen (these has been networks AFAIK supported by Pidgin), sending
 SMS, mail notifications, TV program, weather, games, jabber disk, code
 sharing and dictionaries (although these three can be used without service
 discovery support, but not so smoothly), RSS feeds and SMTP transport.

 If Pidgin does not support service discovery and transports registration,
 then it's pretty bad, because many advantages of the Jabber network are
 gone. (And that's the reason why I stopped using Gaim when I had
 registered my jabber account).

 There is also another significant difference between native
 ICQ/MSN/Yahoo/... support and using transports -- while native support
 provides easier way of implementing "advanced" functionality, using
 transports is just great when I move between computers often. I just set
 my Jabber account and have all the other networks and services available
 in few seconds.

 So the opinion that it is useless to implement transports if we already
 have multiprotocol client is bad because it doesn't provide the same
 functionality and it has other advantages/drawbacks.

 (So I would be very happy to see both multiprotocol support and transports
 support in one client [Pidgin].)

-- 
Ticket URL: <http://developer.pidgin.im/ticket/2194#comment:5>
Pidgin <http://pidgin.im>
Pidgin