I have a table that gets served off to a 3rd party site. Each row has "track" and "hide" checkboxes ... I need to save/update these settings as the user updates their settings so I can call them back later on future visits.
(cookies are not an option... because that is too easily lost and there could be thousands of settings over time)
Let me give you the use case and a scenario:
Table with 100 rows and each row has "track" and "hide". Each row may be associated with one "subject" and multiple rows may have the same subject ... so when you track or hide... it tracks multiple rows (highlights, checks their boxes, and grabs the subject from a row field) OR it "hides" multiple rows based on their subject.
All that is working. (Yes!)
Now, because they could be clicking quickly through... they might track then "untrack" the same subject or hide then "unhide" the same subject all within a very short period of time.
I don't want all those AJAX calls!
So, I need some sort of data storage for the "subjects" that puts them in "track" and "hide" datasets ... removes them out if undone ... and occasionally submits whatever the queued up actions are (if any).
Also, there may be settings grabbed on page load that need undone (the track and hide setting grabbed from the DB that pre-dated that visit) ... so it may not as simple as removing from a data set... there should be an explicit "untrack" & "unhide" submission in those cases to update the DB.
Can you help me wrap my head around this code with an example please!