Hi, 2012/6/9 David Baelde <[email protected]>: > On Sat, Jun 9, 2012 at 1:02 PM, David Baelde <[email protected]> wrote: >> Could it be that we just have no way of telling the buffer that we've >> stopped feeding it? I'd imagine that in that situation we insert a >> break in the buffer, which should make it possible to issue a good >> remaining time estimation. > > I don't have time to test or patch, but this seems plausible: the > #remaining method of src/sources/generated.ml doesn't take breaks into > account. > > Azerty88: sorry for the developpers' talk, and thanks for pointing out > what's probably a bug. Unless you're really interested in fading out > unexpected failures of your HTTP input, due for example to network > lags...
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. 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.. Romain ------------------------------------------------------------------------------ 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
