Rob Evans
Rob Evans
@Ulkuurz That is a very interesting and novel way to solve the problem! Kudos!
I'm rewriting ForerunnerDB from scratch in ES6 with a view to removing all of these annoyances. When I first coded FDB it was as an in-memory store for single page...
@Fadi288 unless browsers increase that limitation then no.
Hmm... Sounds like you probably want an API that the client can talk to every minute to get the signal status and when the page loads, call the API to...
Hmm, I don't suppose you are able to step into the code are you and follow execution? I've not played around with electron so I don't know what it is...
Hmm yeah. You definitely want to wait for a previous save call to complete before asking for another one.
But why save constantly like that? Can't you save once you've got all the items in the collection?
Ahh ok I see where you're coming from. The issue will be that it won't save only changed data, it will attempt to save all data every time you call...
Cool :) I think that the performance issue with saving 50k+ records won't be the actual writing data to disk part but more likely the part that turns the javascript...
For instance, when you do a save we could store 1 record per line in the JSON file so that we could identify the exact data to CRUD from the...