#47: Tick Thread and better scheduling
-------------------------+--------------------------------------------------
Reporter: toots | Owner: toots
Type: Feature | Status: assigned
Priority: 5 | Milestone:
Component: Liquidsoap | Version: 0.3.4+svn
Resolution: | Keywords:
-------------------------+--------------------------------------------------
Comment (by mrpingouin):
Hi,
(I'm just coming back from holidays, trying to catch up on mails/tickets.
Please forgive me if I'm talking to quickly about things that I didn't
study in depth.)
Your approach does not feel quite right... You identified the right needs
for the scheduler, and the difficulty. But difficult doesn't mean
impossible, and I'm afraid your somewhat heavy workaround stays too long
instead of a correct solution.. I propose to close this ticket (but leave
the choice to you) and:
* implement a lighter workaround at the request_source level for the
empty playlist problem (we outlined it already);
* implement something restricted to lastFM for lastFM (so that the extra
thread is not started when you don't use lastFM);
* until somebody implements a clean extension of the scheduler (this can
be done purely passively, without any extra thread).
--
Ticket URL: <http://savonet.rastageeks.org/ticket/47#comment:4>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
