blog

There are two challenges to implementing so-called command chaining, but only one of them is choosing a linguistically appropriate structural standard and parsing it. The other is the underlying difficulty of processing each individual “clause” in sequence, asynchronously. Alex Fritze blogged about how a project like his own Oni could dramatically simplify this underlying process.

Ubiquity, Oni, and Composability:

but I cannot instruct it to give me list of translated google results:

translate (google foo) to German  // doesn't work

Or email me the resulting list:

email(translate (google foo) to German) // doesn't work

…So how does Oni relate to this? Oni is a browser-based “embedded structured concurrency framework”. It allows you to write asynchronous code as if it was synchronous, adding back the kind-of composibility that is lost when juggling concurrent strands of execution (such as e.g. pending XMLHttpRequests) with ‘conventional’ sequential languages.

Related posts:

1. Ubiquity i18n: questions to ask
2. Where’s The Verb?
3. Count command for Ubiquity
4. Writing commands with semantic roles
5. Rolling out the Roles

Related posts brought to you by Yet Another Related Posts Plugin.

Tags: asynchronous, code, composition, JavaScript, Mozilla Planet, recursion, ubiquity

If you enjoyed this post, make sure you subscribe to my RSS feed (optionally with tweets from my Twitter)!

This entry was posted on Wednesday, April 29th, 2009 at 9:41 am and is filed under link. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.