Begasus

Great progress! Keep up the good work!

Zardshard Developer

And now I run into the problem PulkoMandy has been telling me I might encounter. Currently, WebKit’s connection creation code goes something like this:

1. Give me a connection (in our case, a BMessenger)
2. Thanks! I’ll send that off to the other process.
3. Ok, now create the the BLooper and BHandler to receive those messages.

No, we can’t make a BMessenger to a currently non-existent BLooper. WebKit has pretty much ordered the steps in the worst possible way for us! We have to create a BMessenger before knowing what the BLooper that is supposed to receive it is.

Now I see why Rajagopalan had such a complex solution in the GSoC 2019 project. It seems I’ll have to do one of

1. Have a similarly complex solution
2. Modify WebKit’s code
3. Create a new way of messaging in Haiku

4 replies

suhr

Is modifying WebKit code problematic? How often relevant parts of the WebKit code change?

1 reply

nephele Developer

Often. If we edit shared code we need to maintain it very often, or we upstream it. If we do there should be a good reason since webkit doesn‘t maintain our port. : )

PulkoMandy Developer

In this specific case, I’m not sure it changes all that often. And that would be the cleanest soluton. Maybe we should ask WebKit developers about this as well, they may be willing to consider changes as long as it still allows the other platforms to work.