Overview
Feature applications provide The feature applications contained in the Getting Started samples (download) provide in-depth examples of how to use a particular Fabric3 featurefeatures, such as pub/sub eventing and are located under /features. As with the starter applications, a feature application can be built and deployed to one of the server configurations located under /serversserver. For instructions on building the Fabric3 servers, see Starter Applications.
...
| Anchor | ||||
|---|---|---|---|---|
|
This application demonstrates how to use write a logging extension for the Fabric3 low-latency, garbage-free monitor framework. This framework provides extremely high-performance processing of application events such a log data. The monitor framework uses type-safe proxies generated from application supplied interfaces for emitting events. The framework is designed for low-latency applications (where traditional logging solutions are not viable) and is able to persist messages to disk in sub-microsecond time with no object allocation. The sample demonstrates monitor configuration as well as extending the framework to create custom event sinks.
...
For more on timers, see Timer Components.
...
The websocket chat application demonstrates how to use channels to push events to browser clients over websockets. The browser client uses JQuery and JSON to receive events from a server-based channel. After deployment to the single VM runtime, the browser client is available at http://localhost:8181/chat/chat.html.
The sample can also be deployed to a distributed domain. If more than one runtime is launched in a zone, the chat channel will replicate messages to every member in the cluster. This makes it possible for browsers connected via websockets to different runtimes to receive events broadcast by other members in the cluster.
...
.
| Anchor | ||||
|---|---|---|---|---|
|
This sample illustrates advanced wiring techniques including ordered injection and Map-based service references. These features are useful for applications that require support for extension points such as a message-processing service or rules engine that must dispatch to handlers or rule evaluators. A number of patterns are covered, including registries, white board and key-based message dispatch.
...