I have discovered NetKernel at a very late date and I played with it about half a day last weekend. These guys have taken uniform semantics to a new level. Every service, local or remote, is represented by a URI, and you compose services using a declarative * scripting language. You invoke verbs like SOURCE and SINK (analogous to GET and POST) on these URIs, and the kernel understands dependencies and can cache results intelligently.
You create your own services and map them to addresses in the URI namespace.
They also put a lot of emphasis on their available XML pipeline service, and if used properly, there's your engine of application state.
I hope this product can get some attention from REST architects. It's really a unique, REST friendly way to build services.
*My first brush with that language leaves two impressions: a) looks kind of procedural to me, and b) XML is really too verbose to use as a framework for scripting language.
Hugh Winkler holding forth on computing and the Web
- ► 2008 (21)
- ► 2007 (38)
- ► 2006 (39)
- ▼ March (5)