Le Thursday 20 September 2007 08:48:17 David Baelde, vous avez écrit : > The two request queues implement an user-manageable "secondary" queue > built on another abstraction which already has a "primary" queue. This > primary queue is used for example in playlist sources to prepare > (download and check) requests in advance, to avoid failures.
Couldn't it be nice then to seperate this in telnet/socket printing ? Ex: >> request.queue loaded: 14 13 17 awaiting: 18 19 20 21 22 23 24 25 Or perhaps better.. Romain -- The music hits you, But you don't feel no pain
