progress callbacks
Werner Koch
wk at gnupg.org
Mon Feb 10 23:16:45 CET 2003
On Fri, 7 Feb 2003 13:56:13 +0100, Marcus Brinkmann said:
> 1. How can GnuPG determine the size of the file it operates on? For normal
> files, this is easy enough. If it works on a pipe, or another object of
> undetermined size, it could emit a progress based on the amount of data
> already processed. In addition, it would be useful if an option could be
> provided which can be used to set the data length that can be expected over
> the pipe, so that programs like GPGME which provide memory backed data
> objects would not have to deal with the absolute -> percentage conversion
> themselves.
the linefeed replaced by an 'X'. "cur" is the current amount
done and "total" is amount to be done; a "total" of 0 indicates that
the total amount is not known. 100/100 may be used to detect the
end of operation.
So you have to emit 0 for TOTAL and you are free to choose whatever
value for CUR - size of the processes chunk is probably a good value
for CUR.
> 2. If the gpg-agent is used, the responsibility to emit progress status
> messages for long decryption or signing operations would have to be in
> gpg-agent, and forwarded by gpg.
Yep.
> Is that about correct? If yes, would such a feature be ok with the GnuPG
> maintainers? Would it be difficult to implement?
OK.
gpg-agent is soo fast that it will never need to emit progress
messages :-)
Salam-Shalom,
Werner
More information about the Gnupg-devel
mailing list