On 10/15/12 2:05 PM, Jason Duell wrote:
> On 10/15/2012 12:20 PM, Brian Smith wrote:
>> Jason Duell wrote:
>>> Our setup also is less than ideal with multiple processes: see
>> Regarding multi-process NSPR logging, don't we just need to send the
>> log output of child processes to a pipe that is consumed by the
>> parent process, and then have the parent process PR_LOG() what it
>> received with some information tacked on (child process ID)?
> Sure, a pipe would be one solution. Some sort of IPC communication is
>> NSPR_LOG_FILE should NOT work for child processes anyway, because
>> child processes aren't allowed to do disk I/O.
> Right--that's how we're doing it now, and it's not viable long-term.
I'm moving forward with implementing NetLog - for logging events in the
I'm currently using an nsObserverService to do all of the actual
notifying. However, nsObserverService methods are meant to be called
from the main thread. My current implementation posts the LOG calls to
the main thread, but this is obviously not good for performance.
My thinking is that I could extend nsObserverService to allow calls from
any thread, and use another separate thread to call the observer
methods. This thread could be created and active only while logging is
Feedback is appreciated.