gskthreadpool For running things in other threads. A thread pool is an optimization which allows many small jobs to be run in a background thread. Our thread pools are tied to main-loops, and the view process termination as just another kind of event. Task done notification is run in the main-thread. The Main-thread is the thread to which the main-loop belongs, and is the only thread from which the #GskThreadPool methods (eg #gsk_thread_pool_push) may be run. An opaque structure which houses a number of worker threads. A function to be run in the background thread. It may create a return value that will be examined in the main-thread. Anytime run_data is used in this thread must be thread-safe, meaning: either only the background thread is accessing it, or it can be guarded by mutexes. (is that really the plural of "mutex"?) @run_data: data that was passed to gsk_thread_pool_push(). @Returns: the result_data, which will be passed to the #GskThreadPoolResultFunc. A function to be run in the main thread with the result of the background processing. @run_data: data that was passed to gsk_thread_pool_push(). @result_data: data that was returned by the #GskThreadPoolRunFunc. Function to run in the main thread after #GskThreadPoolRunFunc is finished, or if the thread-pool is destroyed before the task can be started. @run_data: data that was passed to gsk_thread_pool_push(). @result_data: data that was returned by the #GskThreadPoolRunFunc, or #NULL if the task had not been started before the thread-pool was destroyed. @main_loop: @max_threads: @Returns: @pool: @run: @handle_result: @run_data: @destroy: @pool: @destroy: @destroy_data: