29 Mar 2013 18:00
v8ken: orthogonally persistent JavaScript
Hi, As some of you may know, my student Gillis has been working for some time on v8-ken, which integrates the CKen [1] library with the v8 Javascript engine. The result is an orthogonally-persistent Javascript engine. This is a key piece of the larger Dr. SES [3] puzzle. I thought I'd send an update of how this work is progressing. A couple of weeks ago, Gillis managed to overcome a few critical bugs that now allow us to successfully restore a JS session from a heap state file. I wouldn't use v8-ken for anything serious at this point, but this is a huge milestone: it's now possible to crash a v8ken process and restart it without loss of either local data, or messages in-flight. v8ken's messaging system is based on that of Ken (reliable, FIFO-ordered messages carried over UDP). The message-passing interface is fairly primitive at this point: simple unidirectional send and receive of JSON-serialized messages, directed to vat IDs. No E-style far references or promises, although that can probably all be layered on top in JavaScript itself. Our long-term goal is to integrate v8ken with node.js, so that we can have an orthogonally persistent HTTP server. We don't have node.js integration yet, but v8ken currently does have ad-hoc support for serving HTTP requests. Consider a v8ken process started with the following script: var counter = 0;(Continue reading)
RSS Feed