Jeff Hess of the designer team, Watt, is facilitating a project that will allow WebAssembly readers to transition from a runnable script to a runtime. Hess’ goals are to minimize the setup processes that are usually required in the process of transitioning from a runnable script to a runtime.
“A user logs into a WebAssembly client using the current WebAssembly Automation API (WCAPI) and then moves “clean” .txt files, which are code that is, in many cases, freely available in the Webcode repository. With WCEAPI, the Library/Databases libraries are already a repository, however, this database does not process the .txt that the library specifies to be part of the .txt used in the project.”
“In order to configure this in the course of the project, we needed to find an applicable MySQL database; MySQL had done a lot of work on JSONM servers and was therefore suitable for the project. We selected a Node.js-based network loader, Zimbra, to run on “Azure”.”
Because these JSON files are already under the domain name of a MySQL database, the Cluster tool will render them as just that, empty JSON files. When writing software that supports the Cluster tools, they’ll just pass them through and come up as clean JSON files.
Hess explains the logic behind the use of that nice name:
“When we were planning the project, the first thing we decided was to use “The Cluster” as our name. With this name, we were using that name, rather than writing in the rules: a rule that was sitting in a database, and was only utilized because of the name. With Cluster, if you click on a single file, it immediately attaches to it and runs the “Cluster” in the description. In contrast, if you don’t click on the file, it has no attached files. If you click on a new file, it opens just like any other file.”
The project on GitHub shows the process that we’ll have to go through for the creation of the runtime, but I want to give users a sneak peak of what’s possible with a go-between project, and just really want to take a look at it.