Sorry everyone, I clearly dropped the ball on the explanation.
vezzy-fnord explains it well. The concept is that you can build and share executable code as freely as you share videos and pictures. Doing that requires a program architecture which contains the code correctly but can also meet a lot of use-cases. My decision was to use HTTP and treat the Workers like Web services, which makes Ajax a uniform interface to local and remote code. Then, it uses link relations to do discovery and configuration.
It's all very early, but please take it with an open mind as a pretty experimental project, and I'll keep making it clearer (and more complete).
(I'm the op) Yaniv is correct. It's HTTP that's JSON-encoded, which makes it faster to parse and serialize when you're in the browser environment. It's otherwise the same as HTTP/1.1.
The 'httpl://' scheme is also under application control, so you can use the API to add and remove hosts in its namespace.
I've been getting some reports of SSL warnings. It appears that some computers don't recognize StartSSL's class 2 CA. I'm going to issue one from their class 1 to see if that solves the issue.
The idea is pretty nifty, although the explanations so far are absolutely terrible, quite frankly. It's hard to get a coherent idea of what this is meant to do.
From what I've gathered, it's a collaborative real-time software development environment where anyone can work on any user-submitted program, which is isolated in a VM. Everything and anything is programmable, so it takes the meaning of "programmable web" to an ultimate.
13 comments
[ 4.3 ms ] story [ 38.1 ms ] threadvezzy-fnord explains it well. The concept is that you can build and share executable code as freely as you share videos and pictures. Doing that requires a program architecture which contains the code correctly but can also meet a lot of use-cases. My decision was to use HTTP and treat the Workers like Web services, which makes Ajax a uniform interface to local and remote code. Then, it uses link relations to do discovery and configuration.
It's all very early, but please take it with an open mind as a pretty experimental project, and I'll keep making it clearer (and more complete).
The 'httpl://' scheme is also under application control, so you can use the API to add and remove hosts in its namespace.
From what I've gathered, it's a collaborative real-time software development environment where anyone can work on any user-submitted program, which is isolated in a VM. Everything and anything is programmable, so it takes the meaning of "programmable web" to an ultimate.
It's still rudimentary, but keep going.