You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel like for actually fixing it, and make it work properly, the ammount of times the application would have to access the pod and refresh the information would be similar to the non existance of the cache.
Furdermore, for the ammount of data we are managing at this moment does not affect that much the performance to really worry about it and spend our valuable time fixing it.
Another thing would be if storing the data, even though it is for a short time, would be aligned with the solid goal. I think that our application should display and give the user tools to modify the data, but not store it, despite the performance when it comes to retrieve data from solid.
I think we should keep the cache and fix it as the amount of information to manage now is small, but might increase in the future, and the performance will be negatively affected
Right now we store the routes in the app not to be retrieve from solid all the time. This has bugs at the moment because it does not update correctly.
We have a few options:
More ideas and opinions are welcome :)
The text was updated successfully, but these errors were encountered: