On Wed, Sep 21, 2011 at 11:10 AM, Stephan Beal <[email protected]>wrote:
> On Wed, Sep 21, 2011 at 5:59 PM, Bill Burdick <[email protected]>wrote: > >> back through a server to get it. The data scheme essentially allows a >> client to emulate a web server for itself (note the mime-type in the >> example). >> > > Thank you for the explanation. Are data URLs always (or normally) > base64-encoded or do they allow arbitrary encodings? (i assume the latter > since the URL contains the encoding name?) If data URLs most commonly use > one format or another, i would strongly prefer to use that same format for > transferring binary over JSON (simply via "portability via ubiquity" > reasons). > No problem! It looks like you can choose base-64 or ascii (with %-escaped hex octets). This covers all of the details: http://en.wikipedia.org/wiki/Data_Uri Bill
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
