I have a collection with 10.000 rows
and my users regulary need to view and search them.
There are 2 use-case:
- “show and search ALL rows”, where I display those rows in an
aldeed:tabularwith custom search-filters
2)** “edit a SINGLE row” where I call another url. The user can edit the row via an
Right now I am using
Flow-Router with Template-Level subscriptions
to init the subscription on a per-url basis - both for 1) and 2).
Right now - the problem is: After going to “url 1) show ALL rows” it takes about 10 Seconds to load those 10.000 records into the client and the user has to look at the spinner. … frustrating.
If the user then selects a row and switches to the “url 2) (edit single row)” the client unloads the 10.000 records
and just keeps a subscription to this 1 record. When he then saves his changes and is redirected to url 1) he AGAIN has to wait for another 10 seconds for those 10.000 rows to load again.
My newbie-question is:
Do you agree that this is nonsense? What are my options?
Is globally publishing those 10.000 rows to all connected users a good idea?