I decided to implement HTML for the cloud today:
static char *publish[] = { (char *)publish_func, "publish", "V", "files", "L", "M", "N", "backup", "password", "pin", 0 };
the syntax is ./BitcoinDarkd SuperNET '{"requestType":"publish","files":[["index.html","text/html"]]}'
the files array has to be in the right order
any file that is referred by another file, must appear first
all html MIME types are supported as long as they fit into the space allowed, which is 1kb for the metadata
the metadata is mostly a list of key locations for the file fragments (* N) and currently this means about 32kb is max size
when it is more debugged, I can boost this to 1mb by nesting it one level and that should be enough
if the second item in the array is missing, it defaults to "text/html"
you can refer to files in your HTML normally and it will search the html folder or the mappings from the files array
I can put standard HTML files, like jquery-2.1.1.min.js in the html folder so there is no need to store that in the cloud
external http:// accesses should work
after a publish command, you will get a 64bit key <URL64> and to display this
http://127.0.0.1:7776/<URL64> should display the HTML included nested file references
if you did a publish with a "password" field defined, then you need to add a ?<password> to the URL or it wont decrypt
if you had both a "password" and "pin" field, then you need to have
http://127.0.0.1:7776/<URL64>?<password>&<pin>
I have the simple case of saving and displaying a simple index.html working, will be debugging automated file -> URL64 mappings
James
