-
Committer:
Alexander Sack
-
Date:
2009-10-22 00:25:19 UTC
-
Revision ID:
asac@ubuntu.com-20091022002519-127dxquicxexil4n
also make a lightweight/not-threaded OperationResultHandler
+ after this patch all not-blocking operations in gwibber are processed in glib
main loop; this should reduce the multi-threading problem to the quite well
confined OperationThread's run method.
+ use OperationResultHandler.process_opdata as glib idle handler for ops
produced in OperationThread
+ drop all uses of output_queue
+ pass operation result handler to OperationManager constructor now that it
schedules the proper callback directly
+ accordingly, do not start the Messages result handler in server.py's Microblog
constructor; instead directly pass it to OperationManager constructor, which
then will use it as a glib idle handler to run the code in mainloop thread