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
To correct what I wrote earlier ...
It seems to be the construction of SWMgr that takes some time, in my
case InstallSource::getMgr().
The actual iteration over the ModMap is fast.
Best regards,
Tobias
Quoting cont...@tklein.info:
Hi,
For now I'm thinking to store this information (Reposit
Hi,
For now I'm thinking to store this information (Repository of a
module) in my own application-level persistence layer.
However, I'm still wondering about the performance of
InstallMgr::getModuleStatus.
It's not a big issue on current desktop PCs with fast SSDs. On my
Windows tablet, t
Hi Troy!
I guess InstallMgr could add a line into the .conf when installing:
InstalledFrom, but that could be a side load, a local repo, another
SWORD application install on a local lan, or one of our remote
sources which might not still host the module.
That would be helpful!
I have 2 u
Ok. In this case (if there are potentially multiple source repo's for
one given module) could a list be returned?
This is quite common for 1:n relationships in databases as well ...
Best regards,
Tobias
Quoting Greg Hellings :
Currently the engine does not intentionally preserve any informat
Hi,
Using the SWORD API, is there an easy way to determine the
remote/source repository a module is coming from?
I haven't found anything in the SWModule class or anywhere else.
This would be my approach without any API method:
1) Get the config entry "PrefixPath" using
SWModule::getConfig
