Open kraeuchi opened 4 years ago
Hi there, Unfortunately have been caught up with work commitments. I think option b might be a good place to start. I will start looking at within the next week
Hi Martin, I have just tested this with 260 records and had no problem retrieving them. I have tested this both with server and client-side Blazor. Any chance you can give some more information? In idea of what you are storing in the record would be great
Hi Wiliam
Thank you for your feedback. I spend this week up in the swiss mountains. If I will be back I can give you more precisely information
what I have tried. Meanwhile I created a method to get junks / ranges of records. It works but isn't production ready because it iterates always through all records at java script side.
According to my investigations the SignalR transfer seams to be the limiting factor.
Until then, Martin
William Tulloch <notifications@github.com> hat am 1. Februar 2020 08:49 geschrieben:
Hi Martin,I have just tested this with 260 records and had no problem retrieving them. I have tested this both with server and client-side Blazor. Any chance you can give some more information? In idea of what you are storing in the record would be great —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
Hello, firstly I thank you very much for your work - really great!
I try to us Blazor.IndexedDB in one of my project but if I try to get more than around 130 Records using GetRecords() an error occours:
Unchecked runtime.lastError: The message port closed before a response was received.
Is this limitation known? I see following possibilites to solve it: a) increase timeout JSRuntime Interop (but is this really the point and it doesn't scale very well) b) to write a method to get a chunk of records, like "give me the next 100 records" c) to expose the cursor directly to Blazor.
What do you think about these ideas and are there plans to improve it? Best regards, Martin