| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
use_tls instance variable.
|
|
|
|
|
|
Next step: atomic function calls (and maybe 'handlers') on state transition.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For example:
iq.reply().error().setPayload(something.xml).send()
|
|
|
|
|
|
|
|
|
