Rob Shortt wrote:
> Dirk Meyer wrote:
>> Rob Shortt wrote:
>>
>>>Use a Twisted reactor for the main/event loop. This should make
>>>freevo more responsive and keep it from blocking on stupid things
>>>like network activity. It will also let us easily turn Freevo main
>>>into a XML-RPC server for receiving communications from
>>> recordserver.
>> It would also make it possible to spend more time searching bugs. Let
>> me explain: I may repeat myself but threads are bad. Remember the bug
>> where Aubin got a STOP event on each second mp3 he played. It worked
>> for me and was a threading bug I found after several hours. Or the bug
>> when playing stopped after 5 seconds? Again, it worked for me and was
>> a threading problem. I spent hours to find these bugs and tried to
>> remove all threads from Freevo. The two remaining threads are checked
>> spending hours of checking.
>
> I agree, threading is a PITA, I dislike them too. I would like to see
> Freevo get rid of all multi-threading.
>
>
>> To make it worse: twisted uses threads I don't know about. I need to
>
> I don't think the Twisted people like threading either. See:
>
> http://www.twistedmatrix.com/documents/current/howto/async
> http://www.twistedmatrix.com/documents/current/howto/threading
I thought twisted is threaded. Now I see that the thread we have is
the generic record plugin. Bad, this needs to be changed. Maybe for
1.5.1 but more on 1.5.1 vs. 1.6.0 in a different mail.
Dischi
--
The Second Law of Thermodynamics:
If you think things are in a mess now, just wait!
-- Jim Warner
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
