commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: [compress] progress monitoring
Date Wed, 30 Mar 2016 08:50:13 GMT
On 2016-03-28, Emmanuel Bourg wrote:

> Le 27/03/2016 18:41, Stefan Bodewig a écrit :

>> Is this a feature we generally want to see in compress? And if so, does
>> the branch make sense or should we tackle this in a different way?

> I like the idea of progress tracking, and the implementation on the
> branch is ok (I'd just add a try-catch around the calls to notify(), so
> an error in a listener doesn't prevent the others from getting the
> notification).

Good catch, thanks.

> That said, maybe the concept of progress tracking is more general than
> [compress] and could be implemented as a decorator stream in [io]

Maybe in addition what I've done since right now notification would
happen at format specific events like starting a new block - this is
something the underlying stream doesn't recognize.

> (along with an approximation of the time left to process the stream).

Hard to say when a stream doesn't know how much data is waiting to get
processed :-)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message