A brief introduction how to use rofl-common

Modules
	A simple controller application: ethswctld

Detailed Description

In this section we provide a few examples, how to use rofl-common and OpenFlow protocol endpoints in a project and all classes and means provided to manage OpenFlow control connections and how to handle incoming and send outgoing OpenFlow messages. ROFL supports various usage scenarios like controller or datapath role and may also serve for building proxy entities. It provides a simple-to-use high level interface to OpenFlow mitigating OpenFlow's complexity in day-to-day operations, but its hierarchical design also allows to replace one or multiple of the higher abstraction layers for getting direct access to the low-level routines. See module Workflow for a more detailed view on ROFL's internal architecture.

a) We start with a simple controller application to demonstrate some core principles named ethswctld (see module above).

b) An advanced datapath element build on top of rofl-common and rofl-pipeline is available as extensible datapath daemon (xdpd)

c) A more complete example of a controller application demonstrating some more advanced strategies for building a useful OpenFlow controller is the base box daemon.