Andreas Büsching wrote:
>> Remember the discussions we had about timer. Should a timer fire again
>> when the same timer is still in progress? Do we schedule the new timer
>> when the callback is started or when it is stopped? Some parts of kaa
>> need the way it is now and it is the same way glib
Hi,
On Fri, 2007-12-28 at 18:22 +0100, Dirk Meyer wrote:
> Andreas Büsching wrote:
> > If I remember correctly I suggested to implemented a twisted-notifier in
> > pyNotifier as I do not like the idea to have a feature in nf_generic
> > that in most case is not used ("un-used" code that requires c
Andreas Büsching wrote:
> Hi,
>
> On Thu, 2007-12-27 at 22:54 +0100, Dirk Meyer wrote:
>> > So why is it important that we select on fds but not do anything
>> with
>> > the events? What happens if we don't call select? i.e. why call
>> > nf_wrapper.step() at all?
>>
>> Problem: kaa notifier is
Hi,
On Thu, 2007-12-27 at 22:54 +0100, Dirk Meyer wrote:
> > So why is it important that we select on fds but not do anything
> with
> > the events? What happens if we don't call select? i.e. why call
> > nf_wrapper.step() at all?
>
> Problem: kaa notifier is running in a different mainloop
> (
Jason Tackaberry wrote:
> On Thu, 2007-12-27 at 21:29 +0100, Dirk Meyer wrote:
>> > What is the behavior of pynotifier with simulate=True? From what I can
>> > see it just causes it to call select() on any fds we're monitoring, but
>> > doesn't do anything else (call timers or dispatchers) or even
