Since the coding standard says "no new serialization formats", you might want to investigate relying on LLSD and using LLSDSerialize::serialize and deserialize with a stringstream. (though note that the "notation" format looks deprecated) This might help take care of a lot of the validation concerns at the same time.
Celi On Tue, Jul 14, 2009 at 2:59 PM, Cypren Christenson <[email protected]>wrote: > > From my initial examination of the relevant code (LLPanelLogin), it > seems like this can be solved by editing the XUI (panel_login.xml) and > then altering the fields stored and retrieved from gSavedSettings. > Since there does not appear to be an object serialization storage > method for gSavedSettings, I'm inclined to store a double-tokenized > string in a form such as: > > John|Doe|<md5 passsword>/Fred|Doe|/Jane|Doe|<md5 password> > > The "higher" token delimiter (the slash character, in that example) > breaks apart each record, and the "lower" token delimiter (the pipe) > breaks apart the three fields in the record. An empty password field > would indicate that a user did not check "save password". Tokenization > would be done using boost::tokenizer.
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
