Hi John,

I've just noticed your code change was implemented in 4.4, but now the old code is back in for 4.5.1 and is again using illegal characters, any idea why the code has been changed?

Thanks,

Lee

I don't think this was ever changed in the core, if you are referring to the clientapicaps file.  The problem with this change is it greatly increases the payload of the page, since instead of one single character serving as a delimiter, it is made up of three.

Regarding the code John is referring to.  He had pointed me in the direction of a js function on the net that allowed for client-side base64 encoding/decoding.  I am always hesitant simply copying someone else's code and claiming it as my own and discussed this with John and the rest of the team at the time.  I am not saying that I will not eventually utilize this code-snippet, I am only saying that I have not spent the time making sure it is not in some violation.  One of the things on my higher priority list is to integrate the clientapi with msajax.  I am about 15% done with this right now.  I hope that their framework will have this functionality already built in, though I haven't seen it yet, but haven't looked very hard either.