| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
in sleek may be loaded. Added optional argument pluginModule that is a string that represents the module the desired plugin should be loaded from.
An exception on plugin loading now also will not cause the program to exit. The exception is caught and loading of other plugins contains.
|
|
|
|
|
|
Next step: atomic function calls (and maybe 'handlers') on state transition.
|
|
|
|
in sleek may be loaded. Added optional argument pluginModule that is a string that represents the module the desired plugin should be loaded from.
An exception on plugin loading now also will not cause the program to exit. The exception is caught and loading of other plugins contains.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
