On 10/23/17 10:30 AM, Jeff Muizelaar wrote:
For the curious among us, what made nsIURI not thread safe in the first place?
There were several aspects to this:
1) Constructing a URI object. This needed a protocol handler, which
could be implemented in JS by extensions. With XPCOM
On 23 October 2017 at 16:21, Anne van Kesteren wrote:
> On Mon, Oct 23, 2017 at 4:01 PM, Valentin Gosu
> wrote:
> > A few weeks ago we landed MozURL. This is an immutable threadsafe wrapper
> > for rust-url.
>
> What is the plan for these issues:
>
>
On 23 October 2017 at 16:30, Jeff Muizelaar wrote:
> For the curious among us, what made nsIURI not thread safe in the first
> place?
>
One of the factors was that as an IDL nsIURI could also be implemented by
JS code in addons, which could only run on the main thread.
For the curious among us, what made nsIURI not thread safe in the first place?
-Jeff
On Mon, Oct 23, 2017 at 10:01 AM, Valentin Gosu wrote:
> Hi everyone,
>
> Threadsafe URLs have been high on everybody's wishlist for a long while.
> The fact that our nsIURI
On Mon, Oct 23, 2017 at 4:01 PM, Valentin Gosu wrote:
> A few weeks ago we landed MozURL. This is an immutable threadsafe wrapper
> for rust-url.
What is the plan for these issues:
https://github.com/servo/rust-url/issues/163
Hi everyone,
Threadsafe URLs have been high on everybody's wishlist for a long while.
The fact that our nsIURI implementations weren't thread safe meant that
hacks had to be used to use a URI off the main thread, such as saving it as
a string, or bouncing back to the main thread whenever you had
6 matches
Mail list logo