|
NetKernel transports detect events occurring in the outside world.
The role of a transport is to adapt a particular event (such as an
incoming HTTP request) to an internal root request and
inject it into an application for processing.
Applications in NetKernel are loosely coupled to transports and in
fact can use multiple transport simultaneously.
An application can start out supporting HTTP and later add JMS
turning it into a message bus application.
NetKernel HTTP Server
|
NetKernel includes a high performance HTTP transport based on
the Jetty HTTP server.
The transport includes a configurable bridge that
collects dispersed information contained in an HTTP request
and places it into a unified root request.
|
SOAP Server
|
SOAP HTTP Protocol binding is a configurable mode of the HTTP transport.
SOAP services are created by routing external SOAP service requests from an external
SOAP interface to an internal NetKernel service endpoint.
|
NetKernel JMS Service Bus
|
JMS services and transport allows NetKernel be used as a peer
on any JMS Enterprise service bus.
The transport supports the development of Message-Driven-Services,
whilst JMS services supports NetKernel applications acting as the
source of JMS messages.
|
NetKernel SMTP / POP Services
|
Integrate your application with email.
Send messages via SMTP or process inbound messages from POP and IMAP email servers.
NetKernel can seamlessly integrate email processing into your application.
|
|
