Don't require a named backend
Naming a backend adds no value to the configuration and only serves to
complicate things. Multiple unamed carbon backends are still allowed.
Documentation updated to reflect the change.
Naming a backend adds no value to the configuration and only serves to
complicate things. Multiple unamed carbon backends are still allowed.
Documentation updated to reflect the change.
Modify whitepsace
Optimize strlen() calls out
Move send buffer size to the top of the file
Remove fold markers
move sources
free name appropriately
add config example and move host definitation out of <Carbon> attribute
initial sync from private repo