OK, because I am a pudgy old Miva scripter who still enjoys the heck out of old, uncompiled MivaScript I get approached by clients wanting me to create/edit/fix antique MivaScript apps. One came to me recently which has overwhelmed my obsolete brain matter.
The client wants to use both crypto payments and PGP stuff [no, he is not messing with illegal stuff he is just more paranoid than a QAnon leader on a good day], and wants to only have ASCII data. Problem is that he wants to export and potentially import dB fields containing those data sets, and each of them seem to contain just about every character in the ASCII set. And as anyone who's worked with crypto stuff knows, even one character out of place means everything fails. I must be missing something very fundamental here trying to eval all the potential characters used in crypto stuff.
So the problem is how to encapsulate that potentially full run ASCII data without the delimiter potentially appearing in the data? Anyone have any experience in this regard (my old friend Ivo has faded) or might be able to offer a perspective on this one?
Thanks!!!
The client wants to use both crypto payments and PGP stuff [no, he is not messing with illegal stuff he is just more paranoid than a QAnon leader on a good day], and wants to only have ASCII data. Problem is that he wants to export and potentially import dB fields containing those data sets, and each of them seem to contain just about every character in the ASCII set. And as anyone who's worked with crypto stuff knows, even one character out of place means everything fails. I must be missing something very fundamental here trying to eval all the potential characters used in crypto stuff.
So the problem is how to encapsulate that potentially full run ASCII data without the delimiter potentially appearing in the data? Anyone have any experience in this regard (my old friend Ivo has faded) or might be able to offer a perspective on this one?
Thanks!!!
Comment