SnowFlowerSittingWolf

Some things bothered me about this thread, I'll clear them up here about json: 1. Json is not useless, its basically the language nearly every RESTFul API and data-driven HTTP-standardized and secure HTTPS API talks in on the internet (XML being another language API talks in, but thats another story). sURLs talk in json when sent a GET request, as an example. Its how data is relayed to/from second life database servers, and external sources, such as a product developer's website for registration information and personalized owner settings stored in an object. 2. Json is not time-critical. It was designed as a web communication protocol to pass data to and from a web-server, and should be used that way. It is similar in concept to what HTML is, and what XML is. If you find yourself using json objects without making http/https requests, you probably should be looking at some other way to store your objects. 3. Json data should be treated with a hard upper limit of 4096 UTF-8 byes in core LSL and 16384 UTF-8 bytes in Mono as part of the request body limit of the LSL web toolkit. LSL is not designed nor optimized to handle json structures larger than this. Most API will never send/accept much more than this if properly designed, anyway, with Second Life in mind. 4. Json serialization/deserialization inclusion in LSL is an essential part of the Second Life LSL web toolkit, and makes all of our lives much easier when dealing with CRUD-model based API and database systems on and off second life. If you've ever dealt with a notecard memory database, you'll be pleased to know you can toss that code out - LSL is Json and RESTFul web HTTP request friendly. 5. Json should never be used as a permanent method of documentstore (datastore). Its simply a communication protocol designed to send objects to/from a more permanent document store, such as an api which stores/retrieves information from a mysql database, sqllite implementation, or nosql implementation that can reply to queries efficiently and process data quickly. It is not optimized for speed, but is for portability. For more information, please visit these help topics: What is Json? (web protocol) https://www.w3schools.com/whatis/whatis_json.asp Making HTTP/Secure HTTPS put/get requests with LSL http://wiki.secondlife.com/wiki/LlHTTPRequest Serializing/Deserializing request bodies with LSL - Json structure to native LSL objects and back: http://wiki.secondlife.com/wiki/Json_usage_in_LSL