Bug 79460 – RunLoop should be an event processing loop for all threads.

• Status: UNCONFIRMED
• Component: WebKit2

[Dongseong Hwang]

RunLoop origins from CFRunLoop of Cocoa that is part of the fundamental
infrastructure associated with threads.
RunLoop can be used as a common event loop on every threads in WebKit.
For example, ScrollThread can use RunLoop in order to remove boilerplate code
related to handle an event loop and its own tasks.

Referential bugs : Bug 66962 , Bug 76751

[Dongseong Hwang]

Created attachment 128677 [details]
patch

[Dongseong Hwang]

If this patch will be passed, I want to apply following classes.
 ScrollingThread
 StorageThread
 FileThread
 DatabaseThread

[Dongseong Hwang]

(In reply to comment #0)
> RunLoop origins from CFRunLoop of Cocoa that is part of the fundamental
> infrastructure associated with threads.
Android Looper is also very similar to CFRunLoop.
Looper and Handler in Android is very comfortable to communicate between threads.
I want something like those.

[Dongseong Hwang]

Created attachment 128696 [details]
ScrollThread patch

This patch can makes ScrollThread succinct.

[Anders Carlsson]

Comment on attachment 128677 [details]
patch

This doesn't make sense, there's no point in calling RunLoop::run() on anything other than the current run loop.

[Dongseong Hwang]

(In reply to comment #5)
> (From update of attachment 128677 [details])
> This doesn't make sense, there's no point in calling RunLoop::run() on anything other than the current run loop.

Yes, only the current run loop calls RunLoop::run() now.
But, if changing RunLoop::run() from static to normal member method, we can use RunLoop in another thread like attachment 128696 [details].

I sumited this patch because I agree with Carlsson's change log of revision 106565.
"Hopefully we'll be able to make ScrollingThread use the new WebCore::RunLoop class eventually."

What point do I need to do more?

[Dongseong Hwang]

I think Bug 51857 is the meta bug of this bug.