- Jun 08, 2010
-
-
Thom Nichols authored
-
- Jun 07, 2010
-
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
context manager now returns a boolean 'result' as the context variable to indicate whether the transition timed out or if you are actually locked when entering the context body
-
Thom Nichols authored
context manager is working but there's a fatal flaw: inside the body of the 'with' statement, there's no way to tell whether or not the transition occurred or timed out.
-
- Jun 04, 2010
-
-
Thom Nichols authored
connect uses the new function-on-state-transition so when the connect method returns you are guaranteed to be either in the 'connected' or 'disconnected' state. Could remove the 'connecting' state except uses it.
-
- Jun 03, 2010
-
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
- Jun 02, 2010
-
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
Nathan Fritz authored
-
Nathan Fritz authored
-
Brian Beggs authored
-
Brian Beggs authored
moddified plugin loading so plugins located outside of the plugins directory 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.
-
Brian Beggs authored
-
Thom Nichols authored
Next step: atomic function calls (and maybe 'handlers') on state transition.
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
Thom Nichols authored
-
- Jun 01, 2010
-
-
Nathan Fritz authored
-
Nathan Fritz authored
-
Lance stout authored
-
Lance stout authored
-
Lance stout authored
-
Lance Stout authored
(cherry picked from commit e1b814f27bf160f20bb30c315ca30769d217482d)
-
Lance Stout authored
Four new events have been added: disco_info - A disco#info result has been received disco_info_request - A disco#info request has been received disco_items - A disco#items result has been received disco_items_request - A disco#items request has been received For disco_info_request and disco_items_request two default handlers are registered. These handlers will only run if they are the only handler for these two events so that multiple responses are not returned and cause errors. In your own handlers for these two events, you can call the default handlers to preserve the static node behaviour as so: self.plugin['xep_0030'].handle_disco_info(iq, True) The forwarded=True will disable the check for other registered handlers. Agents can now dynamically respond to disco requests by using these events. (cherry picked from commit 0fc3381492a8bd75e6a9858539a972334881d8ff)
-
Nathan Fritz authored
-
Nathan Fritz authored
-
Nathan Fritz authored
-
Nathan Fritz authored
-
Nathan Fritz authored
-
Nathan Fritz authored
-
Hernan E Grecco authored
This a simple fix to prevent getting a key error as many plugins add features to Xep_0030. A better fix would be to call pos_init after all plugins are loaded. An even better fix would be to define dependencies for each plugin and registering on demand.
-