Opened 9 years ago
Closed 2 years ago
#12476 closed bug (fixed)
framapad (etherpad) doesn't work.
Reported by: | pulkomandy | Owned by: | pulkomandy |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta4 |
Component: | Kits/Web Kit | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
https://mypads.framapad.org/p/cdl2015-rip-zq4zb7jm?
An error occured while loading the pad NETWORK_ERR: XMLHttpRequest Exception 101: A network error occurred in synchronous requests. in https://mypads.framapad.org/static/js/require-kernel.js? (line 529)
Change History (4)
comment:1 by , 3 years ago
Component: | Applications/WebPositive → Kits/Web Kit |
---|
comment:2 by , 3 years ago
comment:3 by , 2 years ago
I hve confirmed that this works fine with the curl network backend so it's really an issue in our network backend, and very likely caused by the missing implementation of platformLoadResourceSynchronously mentioned above.
comment:4 by , 2 years ago
Milestone: | Unscheduled → R1/beta4 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Fixed by using curl backend in haikuwebkit 1.9.0
Note:
See TracTickets
for help on using tickets.
Etherpad is using platformLoadResourceSynchronously(), which is not implemented in our WebKit http backend.
The difficulty is that currently our code uses an asynchronous listener, that communicates with the main thread by sending BMessages. However, platformLoadResourceSynchronously expects the request to run (and the notifications to be called) while blocking the main thread.
To achieve this, either we add some way to run the protocol loop in an existing thread in blocking mode, or need some special way of communicating between the request thread and the main thread that does not involve BMessage (it can be done with a custom asynchronous listener, for example).