nbxmpp.bosh.AckChecker:
Class for generating rids and generating and checking acknowledgements in
BOSH messages
nbxmpp.dispatcher_nb.Dispatcher:
Why is this here - I needed to redefine Dispatcher for BOSH and easiest way
was to inherit original Dispatcher (now renamed to XMPPDispatcher). Trouble
is that reference used to access dispatcher instance is in Client attribute
named by __class__.__name__ of the dispatcher instance .. long story short:
nbxmpp.idlequeue.IdleCommand:
Can be subclassed to execute commands asynchronously by the idlequeue.
Result will be optained via file descriptor of created pipe
nbxmpp.transports_nb.NonBlockingHTTP:
Socket wrapper that creates HTTP message out of sent data and peels-off HTTP
headers from incoming messages
nbxmpp.transports_nb.NonBlockingHTTPBOSH:
Class for BOSH HTTP connections. Slightly redefines HTTP transport by
calling bosh bodytag generating callback before putting data on wire
nbxmpp.idlequeue.GlibIdleQueue:
Extends IdleQueue to use glib io_add_wath, instead of select/poll In another
'non gui' implementation of Gajim IdleQueue can be used safetly
nbxmpp.simplexml.NodeBuilder:
Builds a Node class minidom from data parsed to it. This class used for two
purposes:
nbxmpp.client_nb.NonBlockingClient:
Client class is XMPP connection mountpoint. Objects for authentication,
network communication, roster, xml parsing ... are plugged to client object.
Client implements the abstract behavior - mostly negotioation and callbacks
handling, whereas underlying modules take care of feature-specific logic
nbxmpp.auth_nb.NonBlockingBind:
Bind some JID to the current connection to allow router know of our
location. Must be plugged after successful SASL auth
nbxmpp.auth_nb.NonBlockingNonSASL:
Implements old Non-SASL (JEP-0078) authentication used in jabberd1.4 and
transport authentication
nbxmpp.roster_nb.NonBlockingRoster:
Defines a plenty of methods that will allow you to manage roster. Also
automatically track presences from remote JIDs taking into account that
every JID can have multiple resources connected. Does not currently support
'error' presences. You can also use mapping interface for access to the
internal representation of contacts in roster
nbxmpp.transports_nb.NonBlockingHTTP:
Socket wrapper that creates HTTP message out of sent data and peels-off HTTP
headers from incoming messages
nbxmpp.transports_nb.NonBlockingHTTPBOSH:
Class for BOSH HTTP connections. Slightly redefines HTTP transport by
calling bosh bodytag generating callback before putting data on wire
nbxmpp.auth_nb.SASL:
Implements SASL authentication. Can be plugged into NonBlockingClient
to start authentication
nbxmpp.proxy_connectors.ProxyConnector:
Interface for proxy-connecting object - when tunnneling XMPP over proxies,
some connecting process usually has to be done before opening stream. Proxy
connectors are used right after TCP connection is estabilished
nbxmpp.smacks.Smacks:
This is Smacks is the Stream Management class. It takes care of requesting
and sending acks. Also, it keeps track of the unhandled outgoing stanzas.
nbxmpp.simplexml.T:
Auxiliary class used to quick access to node's child nodes
nbxmpp.simplexml.NT:
Auxiliary class used to quick create node's child nodes
object:
The most base type
exceptions.BaseException:
Common base class for all exceptions
exceptions.Exception:
Common base class for all non-exit exceptions.
nbxmpp.simplexml.Node:
Node class describes syntax of separate XML Node. It have a constructor that
permits node creation from set of "namespace name", attributes and payload
of text strings and other nodes. It does not natively support building node
from text string and uses NodeBuilder class for that purpose. After
creation node can be mangled in many ways so it can be completely changed.
Also node can be serialised into string in one of two modes: default (where
the textual representation of node describes it exactly) and "fancy" - with
whitespace added to make indentation and thus make result more readable by
human.