projects / henge / kiak.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 01bded3) | patch
now we trigger data channel after setting up events!
authorjordan lavatai <jordanlavatai@gmail.com>
Wed, 5 Jul 2017 17:12:23 +0000 (10:12 -0700)
committerjordan lavatai <jordanlavatai@gmail.com>
Wed, 5 Jul 2017 17:12:23 +0000 (10:12 -0700)
commit44c1e3ad8fd1e594cceebb36a97e3b126b7d6188
tree6efe2e35be58afbd4e4b8b1b1fd2ecf3c0fc6976tree | snapshot
parent01bded344986da59b5b34091b85979e116a85693commit | diff
now we trigger data channel after setting up events!
client.js diff | blob | history
kiak isn't a kernel, it's a json-based filesystem that runs in browser memory and provides filesystem abstractions for general i/o, webrtc, webcrypto and webgl. it also provides a node.js server bridge over a websocket, providing restricted server-side filesystem access. the node.js server acts as a router, using URLs to route messages to the bridged 'remote admin', who then may receive HTTP and TCP connections in the browser. any application written for the kiak browser environment may also run on the node.js server. developed for the HENGE engine, but also an independent project providing a multi-user application framework (e.g. for multiplayer web games, screen sharing, or pair programming). the web-client is also a kiak routing server, so it can act as a host for its own clients, who may recursively act as servers for their own clients over WebRTC, and so on.