During this year, I did my best finalizing the Entrelacs prototype I started few times ago. It has been totally rewritten, now with a 64 bits cell structure which may hold a whole arrow definition, ie. a pair of 24 bits adresses. It also includes a commit journal and a working functional machine which illustrates how I imagine a self-efficient system. This code is now runnable and successfully passes few regression tests.
I've also completly rewritten the project introduction into the form of a manifesto. My plan is to separate and highlight the core ideas I believe in from the code I've authorised. By doing so, I hope to make the Entrelacs project an umbrella project working as a reference for people wishing to explore the paths I went into. I' m nothing like a leader but necessities push me to act so.
Here are my next plans. On the theoretical side, among other things, I plan to work on a peer-to-peer scalable architecture of networked entrelacs system. On the political side, I plan to introduce Entrelacs as a easily self-hostable server of cloud-like applications which may counterbalance corporate-driven cloud services. On the coding front, I obviously plan to embed an http server in my prototype so to serve arrows as REST resources. Of course, it has surprising implications, like merging resources and url concepts into a single one.
All in all, I'm bound to merge the two projects I'm working on. That is Handballer and Entrelacs. My Entrelacs prototype will be an http server publishing the Entrelacs language interpreter I'm working on. But its key feature will be to allow user agents to register a "closure" as an url that the server will call back on invocation. So Handballer will be operated here to open http push connections and convert them into reliable url. This duo will transform Entrelacs into a Restful applications bus, that is a new form of application server to host complex AJAX/COMET web appliances in a very open and transparent way.
