Those are good ideas. I'll have to consider it, but, that would alleviate a lot of my concerns I think.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik Schindler
Sent: Friday, March 26, 2021 11:59 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Application Specific User Settings: How to?
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hello Darren,
Am 26.03.2021 um 14:17 schrieb Darren Strong <darren@xxxxxxxxx>:
I'll have to manage the equivalent of level checks and these API's don't give you a good way to update all profiles' data layout, because you must specify a user profile, if you even have access as a developer to update other profile's data anyway.
I don't see a big deal with that. If you need to keep track of the settings in a data structure anyway, why not use the first one or byte(s) as a "binary level id"?
If new settings are to be added in the data structure with a new program release, always append new fields to the structure. Never change any fields. If changes are needed, abandon the former field and create it anew "behind" all former fields. This will assure backwards compatibility.
If program-id = struct-id, all is fine. Read and write like usual.
If program-id > struct-id, read as usual, write will update the struct to the new level. Worst thing which might happen is that a user-changed setting will be lost.
If program-id < struct-id, ignore data in the profile, reset all do default and if changes are made by the user, write as usual with the older struct-id.
That's how I'd do it. A (to me) good middle way between programming effort to never lose any data no matter what vs. new version = new settings, all is discarded with a new version.
:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
