On 12 Jul, 07:33 pm, tobias.oberst...@tavendo.de wrote:
>>libuv is a giant pile of new, unaudited C code that didn't even have a
>>passing
>>test suite until a month or two ago. Please feel free to write a
>>reactor for it;
>
>> From what I've read, libuv has designed it's API around the pattern
> libuv is a giant pile of new, unaudited C code that didn't even have a passing
> test suite until a month or two ago. Please feel free to write a reactor for
> it;
>From what I've read, libuv has designed it's API around the pattern
A. "do operation and get notified when done"
instead of
B.
Le Jul 12, 2012 à 6:47 AM, exar...@twistedmatrix.com a écrit :
> I think it was a mistake to try to make it possible to use
> twisted.python.log free-threaded. I think we should think about getting
> rid of this claimed feature. Perhaps it could be replaced with a more
> explicit, probably mo
Le Jul 12, 2012 à 8:26 AM, Tobias Oberstein a
écrit :
>> As far as I know, all of the implementations of POSIX AIO are relatively low
>> quality. They include a number of tricky, low-level constraints (eg, char*
>> to
>> write must be page aligned) as well as some sad functional limitations s
> As far as I know, all of the implementations of POSIX AIO are relatively low
> quality. They include a number of tricky, low-level constraints (eg, char* to
> write must be page aligned) as well as some sad functional limitations such as
> blocking instead of being asynchronous if too many AIOs
For logging could we look at implementing posix aio on platforms that
support it? I would be willing to help code that.
Justin
On Jul 12, 2012 8:51 AM, wrote:
> On 11:32 am, ita...@itamarst.org wrote:
> >On 07/12/2012 05:17 AM, Tristan Seligmann wrote:
> >>3) log observers should expect to be i
On 11:32 am, ita...@itamarst.org wrote:
>On 07/12/2012 05:17 AM, Tristan Seligmann wrote:
>>3) log observers should expect to be inovked in non-reactor threads,
>>making this a Mantissa bug.
>In theory this is the case - the logging howto says "The observer needs
>to be thread safe if you anticipat
On 07/12/2012 05:17 AM, Tristan Seligmann wrote:
> 3) log observers should expect to be inovked in non-reactor threads,
> making this a Mantissa bug.
>
In theory this is the case - the logging howto says "The observer needs
to be thread safe if you anticipate using threads in your program." The
A
When an error occurs in a database connection thread, adbapi invokes
log.err from that thread, which in turns causes log observers to be
invoked in this thread. Mantissa's TracebackCollector has a log
observer which logs items as Items in an Axiom store; this means that
the log observer tries to ru
