Hi Troy,
Thanks for the feedback! 😊
Yes, lazy loading in SWMgr would probably help. Looking forward to getting this
improvement in place.
Regarding my original question:
With my newly developed method getRepoModuleIds I can now also rather quickly
(< 1s) determine the repository a module belong
It would be an uphill task to persuade other repo managers to do that.
Sent from ProtonMail Mobile
On Mon, Sep 30, 2019 at 16:24, ref...@gmx.net wrote:
> Less onerous , but of course also less accurate, we could introduce a conf
> entry which could be automatically applied during module uplpad
Less onerous , but of course also less accurate, we could introduce a conf entry which could be automatically applied during module uplpadSent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: Re: [sword-devel] Determining the reposito
Hi Tobias,
Yes, thank you for all this. We certainly could optimize SWMgr c-tor for large
repos. My guess is that the creation of every SWModule for large repos is
taking the time. Many impls of SWModule check their data files on c-tor. SWMgr
also adds all the filters to each SWModule. All of th
Hi,
in my Sword backend (node-sword-interface) I've now implemented a new
method isModuleAvailableInRepo:
bool isModuleAvailableInRepo(std::string moduleName, std::string
repoName="all");
This method avoids the creation of a SWMgr instance (which is slow for
large repos), but just quick
