Re-forwarding yet again...
-- Forwarded message --
From: Amanda Walker [EMAIL PROTECTED]
Date: Wed, Nov 5, 2008 at 10:22 PM
Subject: Re: [chromium-dev] Re: OS X IPC Design doc
To: chromium-dev@googlegroups.com
On Wed, Nov 5, 2008 at 10:11 PM, Amanda Walker [EMAIL PROTECTED]
And one more from last night that got dropped:
-- Forwarded message --
From: Amanda Walker [EMAIL PROTECTED]
Date: Wed, Nov 5, 2008 at 10:42 PM
Subject: Re: [chromium-dev] Re: OS X IPC Design doc
To: chromium-dev@googlegroups.com
On Wed, Nov 5, 2008 at 10:32 PM, [EMAIL
On Fri, Oct 31, 2008 at 3:11 PM, [EMAIL PROTECTED] [EMAIL PROTECTED]wrote:
Thanks for your great feedbacks. Please see my comments below.
On Oct 29, 2:03 pm, Nick Baum [EMAIL PROTECTED] wrote:
*Permissions:* I agree with Brian that drag-n-drop is somewhat clumsy for
granting permissions
It sounds like things are still fairly speculative...
Since Linux and Darwin are so similar, it seems like it would be very nice
to share code.
Have you looked at using unix-domain sockets and sendmsg to achieve the
equivalent of DuplicateHandle? Since we always use DuplicateHandle in one
On Thu, Nov 6, 2008 at 2:05 PM, Amanda Walker [EMAIL PROTECTED] wrote:
On Thu, Nov 6, 2008 at 4:45 PM, Darin Fisher [EMAIL PROTECTED] wrote:
It sounds like things are still fairly speculative...
Well, performance differences are not speculative, though we don't know
what the effect on
I thought that was the original plan, waiting until traffic died down. I'm
good with it.
Avi
On Thu, Nov 6, 2008 at 5:33 PM, Evan Martin [EMAIL PROTECTED] wrote:
#chromium has almost no traffic and easily 90% of the traffic it does
have are developer questions.
I propose we kill off
Is the code running on this thread short lived? Would it make sense
to use the worker pool?
On Thu, Nov 6, 2008 at 10:57 PM, Wan-Teh Chang [EMAIL PROTECTED] wrote:
On Thu, Nov 6, 2008 at 12:33 AM, Ibrar Ahmed [EMAIL PROTECTED] wrote:
Hi,
I am currently working on (Issue 4152:
...
When the background task is allowed to start, it will continue to run
even when the browser is exited. Next time when the system is started
and the user logs in, the background task will run automatically
without any re-authorization since the permission has already been
granted
