> More generally, tabs, iframes, workers, etc. all make up a set of browsing
contexts. The question then becomes: what set of browsing contexts should
be the unit of debugging? Or put differently: what set of browsing contexts
should be under control of the debugger, so that pausing the debugger
pa
Thanks for the info about mozilla::pkix. I think that webpki looks like it
might be the right answer for a certificate library.
I 100% understand the desire to use a pure Rust TLS library for Servo, but
I think we need to not ignore the fact that there isn't one right now. Ring
implements the cryp
On Tue, Sep 6, 2016 at 11:38 AM, Jack Moffitt wrote:
> > Outside of the NSS team, who has more confidence in NSS than *ring* +
> > webpki + Rustls, BoringSSL, or OpenSSL? And, what is the reasoning?
>
> I think the assumption here is that many people outside the current
> Rust community would hav
> Outside of the NSS team, who has more confidence in NSS than *ring* +
> webpki + Rustls, BoringSSL, or OpenSSL? And, what is the reasoning?
I think the assumption here is that many people outside the current
Rust community would have more confidence in NSS, BoringSSL, or
OpenSSL than Ring + rust
Jack Moffitt wrote:
> Since we currently use OpenSSL via hyper, this means the trait would
> be used there. I assume we'll also need a trait for the pki parts (and
> those are in Servo I think).
>
> With that boundary we could replace OpenSSL with NSS and then add
> others as they come online. Th
[not sure if this will make it through to the list]
On 06/09/16 21:35, Jack Moffitt wrote:
I haven't quite settled on my dissertation topic, but my top contender at
the moment involves property-based (i.e. QuickCheck style) generation of
random web pages/stylesheets.
A sort of subtask of this
On Thu, Sep 1, 2016 at 10:43 AM, Jack Moffitt wrote:
> mozpkix was the proposal, which Brian is also an author of. Brian, why
> exactly is mozpkix hard to wrap? Specific examples may help us
> understand Rust / C++ limitations. If that library is hard enough to
> wrap, then it might be less work
> I haven't quite settled on my dissertation topic, but my top contender at
> the moment involves property-based (i.e. QuickCheck style) generation of
> random web pages/stylesheets.
A sort of subtask of this which would be extremely useful is taking a
known rendering problem and producing a minim
This sounds right to me. Isn't this pretty much a ScriptThread?
There are a lot of different ways to present the big picture. Sometimes you
want workers to stop and be paused along with the main thread; at other
times, you'd like the worker to continue running. (GDB took a
stop-the-world approach,
I think that each unit of sequential execution should get its own debugger
server (so a (same origin?) related browsing context). Then if we want to
present a unified interface, we can race-ily pause workers (and cross
origin iframes?) and coalesce these things in the UI or via a supervisor
task.
> NSS doesn’t currently support building as static libraries. Do you think it
> would be better to try to use the system NSS or ship the libraries?
Depending on the system one exclusively is one reason why our OpenSSL
bindings suck. So we have to have it built by Cargo as a fallback.
jack.
_
On Tue, Sep 6, 2016 at 4:35 AM, Boris Zbarsky wrote:
> On 9/5/16 8:17 AM, Till Schneidereit wrote:
>
>> I don't think it makes too much sense to be able to pause completely
>> independent browsing contexts that can't possibly interact with each
>> other.
>>
>
> There is no such thing. They can a
NSS doesn’t currently support building as static libraries. Do you think it
would be better to try to use the system NSS or ship the libraries?
Diane
> On Sep 5, 2016, at 10:16, Ms2ger wrote:
>
> On 26/08/16 02:13, Diane Hosfelt wrote:
>> Proposed Development
>>
>> I propose to create Rust b
13 matches
Mail list logo
