Editing NetKernel (section)

==Concepts==
===Resource===
A ''resource'' is identifiable information within a computer system. Resources are an abstract notion and they cannot be manipulated directly. When a resource is requested, a concrete, immutable ''representation'' is provided which captures the current state of the resource. This is directly analogous to the way the World Wide Web functions. On the Web, a URL address identifies a globally accessible resource. When a browser issues a request for the resource it is sent a representation of the resource in the response.

===Addresses===
A resource is identified by an ''address'' within an ''[[address space]]''. In NetKernel, [[Uniform Resource Identifier]] (URI) addresses are used to identify <!-- want a link to a definition --> all resources. Unlike the Web, which has a single global address space, NetKernel supports an unlimited number of address spaces and supports relationships between address spaces.

NetKernel supports a variety of [[URI scheme]]s and introduces new ones specifically applicable to URI addressing within a software system.

===Request===
The fundamental operation in NetKernel is a ''resource request'', or ''request''. A request consists of a resource URI address and a ''verb''.
Supported verbs include SOURCE, SINK, NEW, DELETE, EXISTS and META. Each request is dispatched to a [[Monolithic kernel|microkernel]] which resolves the URI address to a physical endpoint and assigns and schedules a [[thread (computer science)|thread]] for processing. When the endpoint completes processing the microkernel returns the response to the initiating client.
<!--
Because the association of a request and the execution thread is handled by the kernel and is not visible to the upper layers, NetKernel applications can achieve full utilization of all cores on multi-core computers.

Not really. We should say that the isolation allows for sync/asych? What is the fundamental reason it scales with cores? REST-ish ness?
-->