83 lines
4.1 KiB
HTML
83 lines
4.1 KiB
HTML
<!doctype html>
|
|
<html lang="en-us">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<link rel="shortcut icon" href="data:image/x-icon;," type="image/x-icon">
|
|
<link rel="stylesheet" href="common/testing.css"/>
|
|
<title>sqlite3 WASM Testing Page Index</title>
|
|
</head>
|
|
<body>
|
|
<header id='titlebar'><span>sqlite3 WASM test pages</span></header>
|
|
<hr>
|
|
<div>Below is the list of test pages for the sqlite3 WASM
|
|
builds. All of them require that this directory have been
|
|
"make"d first. The intent is that <em>this</em> page be run
|
|
using:</div>
|
|
<blockquote><pre>althttpd -page index.html</pre></blockquote>
|
|
<div>and the individual tests be started in their own tab.</div>
|
|
<div>Warnings and Caveats:
|
|
<ul class='warning'>
|
|
<li>Some of these pages require that
|
|
the web server emit the so-called COOP and COEP headers. The
|
|
default build of althttpd <em>does not</em>.
|
|
</li>
|
|
<li>Any OPFS-related pages require very recent
|
|
version of Chrome or Chromium (v102 at least, possibly
|
|
newer). OPFS support in the other major browsers is
|
|
pending.</li>
|
|
<li>Whether or not WASMFS/OPFS support is enabled on any given
|
|
page may depend on build-time options which are <em>off by
|
|
default</em> because they currently (as of 2022-09-08) break
|
|
with Worker-based pages. Similarly, WASMFS does not work on
|
|
some platforms, e.g. Raspberry Pi 4.
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
<div>The tests...
|
|
<ul id='test-list'>
|
|
<li><a href='demo-123.html'>demo-123</a> provides a
|
|
no-nonsense example of adding sqlite3 support to a
|
|
web page. </li>
|
|
<li><a href='demo-123-worker.html'>demo-123-worker</a> is the
|
|
same as <code>demo-123</code> but loads and run sqlite3 from
|
|
a Worker thread.</li>
|
|
<li><a href='testing1.html'>testing1</a>: sanity tests of the core APIs and surrounding utility code.</li>
|
|
<li><a href='testing2.html'>testing2</a>: Worker-based test of OO API #1.</li>
|
|
<li><a href='testing-worker1-promiser.html'>testing-worker1-promiser</a>:
|
|
tests for the Promise-based wrapper of the Worker-based API.</li>
|
|
<li><a href='batch-runner.html'>batch-runner</a>: runs batches of SQL exported from speedtest1.</li>
|
|
<li><a href='speedtest1.html'>speedtest1</a>: a main-thread WASM build of speedtest1.</li>
|
|
<li><a href='speedtest1-worker.html'>speedtest1-worker</a>: an interactive Worker-thread variant of speedtest1.</li>
|
|
<li><a href='speedtest1-wasmfs.html'>speedtest1-wasmfs</a>: a variant of speedtest1 built solely for the wasmfs/opfs feature.</li>
|
|
<li><a href='speedtest1.html?vfs=kvvfs'>speedtest1-kvvfs</a>: speedtest1 with the kvvfs.</li>
|
|
<li><a href='demo-kvvfs1.html'>demo-kvvfs1</a>: very basic
|
|
demo of using the key-value vfs for storing a persistent db
|
|
in JS localStorage or sessionStorage.</li>
|
|
<li><a href='scratchpad-wasmfs-main.html'>scratchpad-wasmfs-main</a>:
|
|
experimenting with WASMFS/OPFS-based persistence. Maintenance
|
|
reminder: we cannot currently (2022-09-15) load WASMFS in a
|
|
worker due to an Emscripten limitation.</li>
|
|
<li><a href='test-opfs-vfs.html'>test-opfs-vfs</a>
|
|
(<a href='test-opfs-vfs.html?opfs-sanity-check&opfs-verbose'>same
|
|
with verbose output and sanity-checking tests</a>) is an
|
|
experiment in implementing a syncronous sqlite3 VFS proxy
|
|
for a fully asynchronous backend interface (namely OPFS),
|
|
using SharedArrayBuffer and the Atomics APIs to regulate
|
|
communication between the synchronous interface and the
|
|
async impl.
|
|
</li>
|
|
<!--li><a href='x.html'></a></li-->
|
|
</ul>
|
|
</div>
|
|
<style>
|
|
#test-list { font-size: 120%; }
|
|
</style>
|
|
<script>//Assign a distinct target tab name for each test page...
|
|
document.querySelectorAll('a').forEach(function(e){
|
|
e.target = e.href;
|
|
});
|
|
</script>
|
|
</body>
|
|
</html>
|