-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expand cache services #106
Comments
|
@kilchenmann Does the endpoint already exist or does it have to be added? |
I'm sorry, didn't saw your previous answer.
Hm, it's a mistake from my side. there is no route or endpoint to get project specific groups. We have to use the |
@kilchenmann Do we still need a user cache then? |
Not sure. I have to run this request many times — not only to list all users. I need a list of all users also in the user-form to keep email and username unique. I compare new entries with the existing ones. But I can make my one cache for this. |
I think I could make a simple cache in the admin endpoint that requests all users when the endpoint is created and stores them all so you can ask for specific users without any further request to Knora. Of course, when user data changes or new users are added, the entries have to be updated. I think this use case is simpler than the ones I have implemented so far so I will make a separate class for this. |
Keep in mind, that only system admin or project admin get an answer from usersEndpoint.getUsers. |
good point, so you need to log in. I will think of a good way to do this. |
Hm, but I don't think we'll need the list of all users outside of the admin interface. So, your solution should be fine. |
So we would have a |
Can you expand the cache service with the following methods:
The text was updated successfully, but these errors were encountered: