That's one failure point. The download goes to a staging folder. If the
download completes then any existing installed version module is removed and
the staging data is copied. There are possible failure points after the
download. If you are hinting at digest sum checks on the data, no we don't
Does libsword assume that a module install or update is successful
because there was no interruption in connection?
On Tue, Sep 27, 2022 at 4:51 PM Tobias Klein wrote:
>
> Thank you, Troy!
>
> Well, it's probably just my developer's mind ... thinking that something
> could go wrong with a
Thank you, Troy!
Well, it's probably just my developer's mind ... thinking that something
could go wrong with a module update and one may want to revert back to a
previous version.
Best regards,
Tobias
Am 27. September 2022 21:54:22 schrieb "Troy A. Griffitts"
:
Hi Tobias. Well, adding to
Hi Tobias. Well, adding to the API wouldn't be a significant change there. What
would be significant is retaining previous versions in the remote repository. I
doubt we can get people to offer every version of their texts. Updates are
usually bug fixes and if they are not simply this, we
The biggest problem with that would seem to be that the server only keeps
the current version. It doesn't keep older versions in place (or, at least
it hasn't in the past)
--Greg
On Tue, Sep 27, 2022, 14:37 Tobias Klein wrote:
> Hi Troy,
>
> As I am thinking about module upgrade support for
Hi Troy,
As I am thinking about module upgrade support for Ezra Bible App
(currently not implemented) I am also (once more) asking myself why
there isn't an API for installing arbitrary module versions with InstallMgr.
The two additional use cases that I would like to have in the SWORD
