Mercury-IM/Smack
Mercury-IM/Smack
1
0
Fork 0
mirror of https://codeberg.org/Mercury-IM/Smack synced 2024-11-16 12:12:06 +01:00
Code Issues Releases Wiki Activity

Couple of fixes in providers.md

Browse source 
Mixed tabs and spaces fixed and made list of extension providers for
standard packets nested.
This commit is contained in:
Andrey Starodubtsev 2016-01-18 21:22:34 +03:00 committed by Florian Schmaus
parent 35ba917728
commit f8d04262c3
1 changed files with 32 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
documentation/providers.md
View file

@ -15,7 +15,9 @@ There are two types of providers:
* `Extension Provider` -- parses XML sub-documents attached to packets into PacketExtension instances. By default, Smack only knows how to process a few standard packets and sub-packets that are in a few namespaces such as: * `Extension Provider` -- parses XML sub-documents attached to packets into PacketExtension instances. By default, Smack only knows how to process a few standard packets and sub-packets that are in a few namespaces such as:
* jabber:iq:auth * jabber:iq:auth
* jabber:iq:roster * jabber:iq:roster
* jabber:iq:register There are many more IQ types and extensions that are part of XMPP standards, and of course an endless number that can be added as custom extensions. To support this, an extensible parsing mechanism is provided via Smack and user build providers. * jabber:iq:register
There are many more IQ types and extensions that are part of XMPP standards, and of course an endless number that can be added as custom extensions. To support this, an extensible parsing mechanism is provided via Smack and user build providers.
Whenever a packet extension is found in a packet, parsing will be Whenever a packet extension is found in a packet, parsing will be
passed to the correct provider. Each provider must implement the passed to the correct provider. Each provider must implement the