.... or 'optimized', I suppose, if you're West of the Atlantic :-)

Anyway, I found encode_json was really slow when encoding a decent sized array of maps (output JSON aprox 125k), so I did some work on it and my modified version is >2x faster for the data I was using it with. I've submitted it as a feature request to Rhinotrac: http://www.lassosoft.com/rhinotrac?id=7750

Warning: on my test data my modified tag produced the same result as the LassoSoft one, but I haven't tested this all that extensively. Use at your own risk! I plan to replace the built-in encode_json, but if you want to run it as encode_json2 for example, don't forget to find & replace all the internal, recursive calls to encode_json.

Any further ideas for optimisation (within LassoScript, ie without using some external C or Java library) would be welcome, and could perhaps be submitted as comments to the Rhinotrac article.

James
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso Lasso@lists.lassosoft.com
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>