Second State
  • What is Second State?
  • Server-side WebAssembly
    • Why?
      • WebAssembly vs native code
    • Getting started
      • VS Codespaces
      • The ssvmup tool
    • Rust functions in Node.js
    • Access system resources
      • WASI
      • The storage interface
      • The inference interface
    • Examples and use cases
      • Encryption and decryption
      • Machine learning
      • Artificial intelligence
    • SSVM Performance
  • Function as a Service
    • Getting started
      • Context
      • Send result to another service
    • Input and output
      • JSON argument
      • Binary argument
      • Multiple arguments
      • Argument from a URL
      • JSON return value
      • Binary return value
      • Redirect return value
    • Stateful execution
  • Related technologies
    • Deno, Rust and WebAssembly
    • A Rusty hello world
    • Rust and WebAssembly
    • WebAssembly in the browser
    • Access JavaScript from Rust
    • How to Learn Rust Without Installing Any Software
    • How to Publish a no-code website in 10 minutes
Powered by GitBook
On this page

Was this helpful?

  1. Server-side WebAssembly

Access system resources

How to access resources outside of the WebAssembly sandbox

PreviousRust functions in Node.jsNextWASI

Last updated 4 years ago

Was this helpful?

This page is outdated. Please visit here for the most up-to-date content.

The WebAssembly VM provides a sandbox to ensure application safety. However, this sandbox is also a very limited "computer" that has no concept of file system, network, or even a clock or timer. That is very limiting for the Rust programs running inside WebAssembly.

In the Second State VM (SSVM), our innovation is a set of standard and proprietary (still open source) extensions that allow WebAssembly bytecode applications to access system and external resources. Read on!

WASI
The storage interface
The inference interface