Components are the main parts of HellHound systems. Basically each components should be an implementation of IComponent. The protocol which defines a component functionality. By default HellHound implements IComponent protocols for hashmaps only. So we can define components in form of maps.

A very light weight and effecient implementation of clojure components.

transform component is a really simple component to transofrm the incoming data and send the result to the output stream.

The default web/websocket server component of HellHound.

This namespace contains core functions which are required by the whole framework in order to operate. Functions which provide easy way to read application configurations based on current environment. Default environment is development. In order to change the environment you need to set the HH_ENV environment variable to new value like production.

This namespace contains default values for HellHound configuration

Several helper functions to make life easier when using then hellhound configuration.

Parser functions for hellhound edn configuration files live in this namespace. This namespace contains several helpers functions to load a edn configuration file from classpath.

This namespace contains several shortcuts and helpers to work with HellHound’s HTTP features such as router, websocket, etc.

A collection of useful Ring handlers to be used with a Ring router. In case of HellHound, hellhound.http.route.

HellHound’s http router namespace. DOCTODO

Websocket module of HellHound is responsible for creating a websocket server on top of Immutant server and dispatch the event coming from clients to event-router and send back the result

Each packer should implement IPacker protocol. For more information and an example checkout hellhound.http.websocket.json namespace.

Pretty simple IPacker implementation for JSON data.

I18n features of HellHound is based on [tempura](https://github.com/ptaoussanis/tempura The initialize-i18n function should be called at the beginning of the application in order to set the default configuration and dictionary.

Different types of log formatter functions to be used with timbre for different environments.

This namespace contains several helper function to help users to produce a ring response.

Utility namespace for spec management and validation in HellHound.

Systems are the most important thing in the HellHound ecosystem. Systems define how your application should work.

All the functions for managing system state live in this namespace. You won’t need to use this namespace directly unless you really know what’s your doing.

TODO

System’s workflow a vector describing the dataflow of the system. Components have an input and an output stream. Each stream is a manifold.stream. HellHound connects io of each component to another component based on the desciption given by the :workflow of the system.