| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
the (few\!) plugins that actually used them.
|
|
they seem to duplicate behavior or be largely unused for their intended purpose.
|
|
|
|
|
|
is provided.
|
|
be sent prior to session establishment.
|
|
|
|
|
|
|
|
|
|
called while a transition is in-process
|
|
did not achieve their lock condition afterwards.
|
|
|
|
|
|
|
|
|
|
|
|
'connecting' state from setStream method
|
|
|
|
lock was acquired in a long-running transition
|
|
|
|
the __future__ imports that were removed.
|
|
Conflicts:
sleekxmpp/__init__.py
sleekxmpp/basexmpp.py
sleekxmpp/stanza/error.py
|
|
|
|
|
|
there to complete auth. If not a failed_auth event is dispatched and the socket disconnected.
|
|
multiple times. This caused issues when trying to reconnect. A handler for the auth mech would get added each reconnection attempt, causing digest-md5, success and failure to be called x times for each x number of retries.
Handlers for sasl authentication as well as success and failure are now added during the __init__ method.
|
|
unicode_literals to get it working correctly. Also some improvments for the prioroity message sending.
|
|
|
|
|
|
reconnecting in another thread before the socket.close call occurred. Now we're locking the state machine until the disconnect routine completes.
|
|
exits.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
lines
|
|
|
|
indicate whether the transition timed out or if you are actually locked when entering the context body
|
|
'with' statement, there's no way to tell whether or not the transition occurred or timed out.
|
|
returns you are guaranteed to be either in the 'connected' or 'disconnected' state. Could remove the 'connecting' state except uses it.
|
|
|
|
limbo
|
