I took a deep dive into CapnWeb. What I expected to find was a browser-first Cap'n Proto successor with rigid schemas replaced by flexibile JSON-compatible data structures. What I found instead was a pared-down pairwise protocol with an interesting expression format.
OCapN on the otherhand has the three-way protcol interactions with a flexible data model with object reference stability.
| (define-values (a-vat a-netlayer a-mycapn) | |
| (make-new-node "a")) | |
| (define-values (b-vat b-netlayer b-mycapn) | |
| (make-new-node "b")) | |
| (define (^greeter _bcom our-name) | |
| (lambda (their-name) | |
| (format #f "Hello ~a, my name is ~a" their-name our-name))) | |
| (define (^echo _bcom) |
🚧 Work in progress.
An implementation of the OCapN protocol.
Includes codecs for Syrup encoded messages.
| /** | |
| * A LazyPromise doesn't run its executor until .then, .catch, or .finally is called, | |
| * or the promise is awaited. | |
| * Unfortunately, `@endo/promise-kit`'s isPromise returns false for instances of LazyPromise. | |
| * However, LazyPromise instances will return true for instanceof Promise. | |
| */ | |
| export class LazyPromise extends Promise { | |
| #isListening = false; | |
| #executor; |
| . | |
| . | |
| ,d88b, . __..- | |
| 888888 . .--SEAL:. | |
| `?88P' . __ ,'WWII::. | |
| .MW:`-. /WWII::.. | |
| . _.MWII:'. `. . ,'WII::.. | |
| _.-MWII::'. `-. ,'WWI::. | |
| . _..vvvv,'WWII::' `.'WII::. | |
| ,-'WI:'''/WII:'. \WI:. |
| #!/usr/bin/env node | |
| const { promisify } = require('util') | |
| const sass = require('sass') | |
| const { promises: fs } = require('fs') | |
| const vm = require('vm') | |
| // example() | |
| // async function example(){ | |
| // const vmContext = vm.createContext() |
| syncing geth on digital ocean | |
| - name: eth2-mainnet-00 | |
| - sync time: (failed to sync, bound by disk perf) | |
| - region: fra1 | |
| - type: s-8vcpu-16gb | |
| - primaryDb: attached volume | |
| - ancientDb: attached volume | |
| - price vps: $0.119/hr | |
| - price volume: $0.052/hr 350gb |
| https://www.redfin.com/OR/Portland/6109-SW-Thomas-St-97221/home/173018992?utm_source=android_share&utm_medium=share&utm_nooverride=1&utm_content=link | |
| https://www.redfin.com/OR/Portland/3246-SW-Cascade-Ter-97205/home/26369492?utm_source=android_share&utm_medium=share&utm_nooverride=1&utm_content=link |
| hi guybedford/ | |
| i really enjoyed your blog post https://guybedford.com/secure-modular-runtimes.html | |
| here's some quick notes comparing your proposal and lavamoat in its current form (https://github.com/lavamoat/lavamoat) | |
| these differences represent lavamoat currently, and can easily be changed with input from smart folks like yourself | |
| ### basic runtime structure | |
| [exactly] "this runtime can fully restrict high-level capability access from packages for third-party code running in the same process" | |
| [exactly] "That this runtime can support an onramp from the existing JavaScript ecosystems, which is crucial for adoption. " |
