GitLab

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

download: progressbar control, overide file, resume (default)
all: extra options for conditional retrieval

Now headers are reset after each request by default
but there is an option for not reseting headers, in low
level

sharers shows the accounts that share objects with cur account

pithos_sh download is incremental, therefore better than kamaki download

manifest is now a seperated method for uploading
old, naive upload is preserved with --unchunked option

Changed behavior of CLI arguments that are command specific
e.g.
    kamaki server -l list
or
    kamaki -l server list
is now a valid kamaki command

Old apis are added with new organization. For each api
a new _cli.py file provides all relevant cli commands

Allow custom libs to be easily loaded to kamaki CLI
At the moment, everything is given in a conf file and
pre-imported

Merge with koukis-fix

transfer_encoding still unchecked

Missing:
- account_quota/versioning
- container_post with transfer-encoding
- object_put with transfer-encoding
- object_copy with manifest
- adjust object_move/post/delete