> Chuck Esterbrook wrote:
> >
> > - Got rid of WebwarePathLocation usage. A script always knows where
> > it's at with:
> > os.path.dirname(os.path.join(os.getcwd(), sys.argv[0]))
>
> That might work. Good idea.
Whoops, this'll need some work. On Linux, sys.argv[0] will be different
depen
Chuck Esterbrook wrote:
> I ran into a problem where an "import Foo" was picking up the Foo in
> WebKit. Launch.py was previously tweaked to fix this but then got
> tweaked back. However, we don't ever want "import Foo" to assume WebKit.
Because WebKit is a package, any modules in the WebKit p
Geoff Talvola wrote:
>
> I also argued that we'd be better off storing the threads on a stack
> instead of a queue. That way the most recently used threads get
> reused, which may produce slightly better performance. I wonder if
> there's a thread-safe Stack class analogous to the Queue
Testing with WebKit reveals a difference so minimal that it's
not worth it. Same thing for switching to Stacks. So many
other things are going on that the gains in the Queue
processing are insignificant as part of the whole.
Consign this experiment to the 'interesting, but purely
academic"
Tavis,
If you want to take the next step, then you should test it to see if it
makes a noticeable difference in the performance of WebKit. If so, then we
can consider including it in WebKit. I'd leave it up to Chuck to decide if
the improved performance is worth the extra hassle and confusio
