Abort downloading command and related issues

[jsbien]

When the response time of a digital library is slow, djview4poliqarp practically hangs - the possiblity to abort the downloading attempt seems a must.

A long term solution may consist in setting up a proxy e.g. on wbl.klf.uw.edu.pl, so the proxy settings present in djview4 should be preserved.

Last but not least, using a local cache should be considered. The djview4 man page states "Browsing remote DjVu documents with the standalone viewer is less efficient than using the browser plugin. The standalone viewer does not benefit from the browser caching strategies". I understand it affects also djview4poliqarp.

[Michał Rudolf]

I think proxy is set on system base – do we really need a separate proxy settings here? As for local cache, of course this makes a lot of sense, but let's leave it for the last stage, as this may obfuscate some network errors.

As for cancel – can you reproduce any kind of locking error? If so, please put the report on how to reproduce in separate issue. Here you can always reconnect/restart query and locking doesn't happen, so I don't see any reason for abort.

[jsbien]

For consistency with Poliqarp GUI the button "Search" should change to "Abort" for the time of query execution.

I agree that separate command for aborting downloading is not needed, as it can be achieved by a new query.

[Michał Rudolf]

Allow aborting queries. Closes #27.

→ Wiki macro error: Changeset aaa8f0ebf60f not found.