#47: Tick Thread and better scheduling
-------------------------+--------------------------------------------------
Reporter: toots | Owner: toots
Type: Feature | Status: closed
Priority: 1 | Milestone:
Component: Liquidsoap | Version: 0.3.4+svn
Resolution: fixed | Keywords:
-------------------------+--------------------------------------------------
Comment (by mrpingouin):
Nice move, thanks!
Regarding the side effect on add_timeout:
* We don't have recursive functions in liquidsoap. (I'm not against them,
that's just the current status). Plus, returning the new delay is a very
natural thing to do, and a very idiomatic one considering lots of other
APIs. I think we should eventually restore the former behaviour, I'm sure
it's still possible.
* Regarding playslists, is it a fix only for playlists, or does it also
fixes crazy loops in all queued request sources ? If I remember well,
these are two distinct things so we should think about enhancing both now
that we have Duppy.
* Regarding priorities, wouldn't it be equivalent and more simple to say
that we have two priorities: one for non-blocking tasks (telnet,
harbor,..) and one for blocking tasks (downloads) ? If we don't have any
clever idea for the future that requires more than that, simplifying might
be good in order to avoid that someone eventually misunderstands the
priority/scheduler scheme and uses a priority that is not listed in any
queue's priorities and hence can only be managed by the default high-
latency queues.
--
Ticket URL: <http://savonet.rastageeks.org/ticket/47#comment:7>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
