> 3. Attach the file descriptor for the compositor's end of the pipe to
> the compositor event loop, and eliminate the polling.
>
> Thus at the end of this, the renderer end of the Unix socket will be in
> `libuv` land, and the compositor end will be in the OS's native event loop.
I like the over
On 11/2/13 8:26 AM, Niko Matsakis wrote:
At a high level, it seems reasonable, but I don't have a good grasp
over what kinds of messages are going over these channels and with
what frequency. That seems to be crucial with respect to judging
the perf effects of moving to a serialization scheme.
At a high level, it seems reasonable, but I don't have a good grasp
over what kinds of messages are going over these channels and with
what frequency. That seems to be crucial with respect to judging
the perf effects of moving to a serialization scheme.
Niko
On Fri, Nov 01, 2013 at 10:54:32PM -
Hi everyone,
Currently Servo's event loop is a poll model on a fixed timer. This is
done for historical reasons: originally the Rust runtime did not
interoperate very well with native UI event loops and we had no choice.
This is very bad—it precludes putting the browser engine into production
4 matches
Mail list logo
