With LISTING enabled, the list of vocabularies is shown at the root so this page should not load too slow. Doing the API query on the server would help but eventually make jskos-proxy a cache (this is already the case for single-vocabulary deployments). Open question is how to do cache invalidation. Daily restarting the application could be enough.
With
LISTINGenabled, the list of vocabularies is shown at the root so this page should not load too slow. Doing the API query on the server would help but eventually make jskos-proxy a cache (this is already the case for single-vocabulary deployments). Open question is how to do cache invalidation. Daily restarting the application could be enough.