view libpurple/protocols/jabber/JEPS @ 25066:256fbe98f6be

The jabber_register_parse function was looking for the <x> node as a child of the <iq> node instead of the <query> node. (See Chs 4 & 5 of XEP-0077) Somebody (maybe it'll be me?) should probably check that the code for these two cases does what it's supposed to, since I don't think it would have run before now. It also looks like the precedence may be wrong (See Ch 6).
author Elliott Sales de Andrade <qulogic@pidgin.im>
date Sat, 07 Feb 2009 23:45:18 +0000
parents 5fe8042783c1
children 1c542f86dbcf
line wrap: on
line source

0045: IN PROGRESS
	Multi-User Chat
0047: IN PROGRESS
	In-Band Bytestreams
0060: NEED
	Pub-Sub
0071: AWAITING FINAL SPEC
	XHTML-IM
0073: NEED
	Basic IM Protocol Suite
0080: NEED (Do we?)
	Geographic Location Information
0084: NEED
	User Avatars in Jabber
0085: NEED
	Chat State Notifications
0089: WATCH
	Generic Alerts
0093: NEED
	Roster Item Exchange
0100: NEED
	Gateway Interaction (Transports)
0115: WATCH
	Client Capabilities
0117: NEED
	Intermediate IM Protocol Suite