Split aduana into several packages

[kmike]

Just a suggestion: C library, a Python wrapper, Frontera integration and REST API server can be 2 to 4 different packages. What do you think?

Maybe it is fine to combine C library and a Python wrapper in a single repo because this way you'll be able to write tests in Python instead of C.

I haven't looked at it in details, but it may be better to separate REST API from the Frontera backend because people may want to use e.g. Kafka queues instead of REST API, and in this case REST API code brings its own unnecessary dependencies (like falcon, talons and gevent).

[plafl]

I will continue to keep together the C library and the python library, although it's possible to build and install the C library separately (http://aduana.readthedocs.org/en/latest/library.html). If, unexpectedly :), people start to make bindings in other languages I will separate them.

Apart from the library and wrapper there are the two frontera backends (aduana.frontera.Backend and aduana.frontera.WebBackend) and the server. The three could be separated. I will keep them together for the moment because it's more comfortable but if the project grows they could very well move to separate projects.