On Tue, Sep 20, 2011 at 12:26 AM, Joshua Paine <[email protected]>wrote:
> base64 encoding turns binary data into an ASCII-safe (and hence UTF8-safe) > string, so it could be used to prepare binary data for transmission as a > JSON value of string type. Clients could safely treat it as just another > string if they don't understand base64 encoding. > But they're then limited by what they can do with it. base64 is useless if you don't have a decoder. > I'm not trying to tell you what you have to implement, but supporting > base64 for sending and/or receiving binary data doesn't really add much to > the complexity of the API or client requirements. To the C side it's pretty easy, but adding any sort of encoding inherently limits the clients which can use it. There is no reference implementation of base64 for JS, for example (there are impls, though), and JS cannot natively deal with binary data (that's coming in v5 or whatever new version is coming soon). Storing binary bytes in a JS string provides undefined results. The primary clients (mine, at least) will be JS. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
