Clean api in spi section: use of connector and its configuration

Description

There are at least those problems with the current code:
1. paxrunner is probably the most complex but most used connector. Its configuration and the stuff needed for the connector is not cleanly separated (one of the reasons are the quick bugfixes like that requires dynamic port configuration).
This must be cleaner. Testscoverage could be better too.

2. there is no abstract connector that eases writing of connectors.
On problem is that paxrunner comes with a wide range of options and built in url handlers. But other connectors do not.
The absract connector should include the setup of useful (all?) url handlers among other "common" things.

Environment

None

Assignee

Toni Menzel

Reporter

Toni Menzel

Labels

None

Fix versions

Affects versions

Priority

Major
Configure