Transport Hub
With the attention devoted to web systems it easy to forget that the Internet
has a wide range of application protocols.
NetKernel's modular transport architecture allows it to support
applications on multiple transports and in multiple
application domains.
Heterogeneous Transport Server
NetKernel applications are exposed as a set of URI-addressed service interfaces.
The applications themselves know nothing about transports, they simply respond to
NetKernel URI requests on their addresses.
External access to a NetKernel application occurs with and through transports
such as HTTP, JMS, JXTA, and others.
With the use of a simple protocol adapter, all in-bound messages can be normalized
to a URI request within a NetKernel application address space.
This high degree of independence from transports make it extremely easy to
build, test, deploy, and adapt NetKernel applications into new deployment
scenarios and domains
NetKernel's strict separation of protocol and application makes it possible to write a single service
or application and make it available on multiple transports.
Protocol Adapter
This example illustrates NetKernel translating between different protocols.
In this diagram, REST based web service requests are translated into SOAP
messages for a SOAP server.
And, SOAP based web service requests are translated into REST messages
for a REST server.
As with all NetKernel applications, pervasive, intrinsic caching can be used
to accelerate applications.
In this case, if a REST or SOAP message is resent, the potential to cache
the result and not call the server is always present.
