GitLab

kamakicon: an httplib/ObjectPool based connection class

Requests also block if pool is full (used to be just for
responses)

HTTPRequestsXxx objects now use connection pooling
Atually, connections are not pooled, but responses are.

Implementation of connection pooling with httplib not ready yet

Pooling tested in uploads

kamaki now has two packages: cli and clients
cli contains all command line interface code
clients is an indepentand lib that can also used by 3rd parties
minor bugs in comput lib

added flavors_get, images_get/delete/post/put

servers_get/post, networks_get/delete/post/put with generic
arguments id and command are now used by oldern, convenience
calls. E.g.
    networks_get(100, 'action') with try
    GET http:.../networks/100/action
so it is used by list_networks

Seperate Client to Client and HTTPConnection
The later is put in a separate package kamaki.client.connection
It manages headers, params, method, url and data of a connection
but the actuall http connection is not implemented at this
abstract level
There is an HTTPRequest class extention of HTTPConnection in the
same package. It implements connection using requests package
so basicaly it replicates the connection procedure that was used
in kamaki so far.
Minor modifications were nessacary at every client lib package

Setup is now aware of gevent and commands package

Implements HTTPConnection using the requests pypi package