[Pidgin] #10096: remove XMLNode completely

Pidgin trac at pidgin.im
Wed Aug 26 09:45:35 EDT 2009


#10096: remove XMLNode completely
------------------+---------------------------------------------------------
Reporter:  mcepl  |        Type:  enhancement
  Status:  new    |   Component:  libpurple  
 Version:  2.6.1  |    Keywords:  xmpp       
------------------+---------------------------------------------------------
 Actually, when thinking about #9931, I thought about idea somebody
 (darkrain? rekkanoryo?) mentioned on IRC ... why not to get rid of general
 XML management in XMLNode object of libpurple completely?

 Meaning, C programmers have their libraries for using XML already (if
 nothing else, libxml is required for libpurple; is it libxml on all
 platforms?), and number of libraries dealing with XML on Perl and Tcl is
 endless. Why shouldn't plugin programmers just use them?

 Certainly, it might be helpful to have some functions for easy dealing
 with specifics of Jabber XML nodes (parsing IQ nodes, messages, etc.), but
 I don't think for example XMLNode->get_child() has any place in libpurple.

 Moreover, I think that functions/signals getting content from XMPP stream
 should return just stream to be parsed by whatever library is chosen by a
 programmer, so that XMLNode doesn't have to be run through to_str() back
 and forth.

 Or maybe (for starters) XMLNode should be just internal object never to be
 exported to plugins?

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


More information about the Tracker mailing list