On Sat, Jun 9, 2012 at 5:15 PM, Romain Beauxis <[email protected]> wrote: > In normal conditions, breaks are added by the stream decoders. Also, > #remaining in sources/generated calls the buffer's remaining method, > which takes breaks into account.
Right, breaks are taken into account one level deeper, I had missed it. > The solution I was proposing before was to add a break when the buffer > gets under a certain threshold. I think that this is the only way to > have some kind of transition when feeding ends, since we cannot > differentiate network lags and proper end-of-stream.. I find this a bit ugly because the purpose of buffering is to hide network lags, which is defeated if we add such meaningless breaks. Another option, also a bit but in a different way, is to have a mode where we always advertise the current remaining amount of data, and never -1. This way, the transition could kick in without a break, and possibly be interrupted if more data is received in the buffer... Anyway, we still don't have a confirmation that azerty88 is interested in having transitions on network lags. I need to run some tests to see if things do work fine for normal stream termination, and then think some more. David ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
