On Wed, Sep 21, 2011 at 5:27 PM, Bill Burdick <[email protected]>wrote:
> Maybe this is obvious, but a client-side editor could use data-scheme URIs > to display intermediately edited data before you commit it to Fossil. > It wasn't obvious to me, certainly. Naively i will ask: would that provide any benefit to that over e.g. base64-encoding to an arbitrary JSON field? The client has the binary data, so how/where he intends to encode it to (data URL or in the request JSON) is pretty much up to him. Or am i missing the point of the proper use of data urls? -- ----- 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
