Feature/soledad adbapi3

DO NOT MERGE YET
just for testing / pullreq purposes

Up to you. I'm not too familiar with the needs. But if we always want to boostrap it on initialization, it would make sense. If there's some situation in which we want to defer it, it would make sense to leave it as it is now.
This is related with something I'm trying to find a solution for: deferred intialization.
For some situations we're going to need to wait until certain objects have been initialized (or "bootstrapped"). In those cases, it would make sense to have a separated bootstrapping function that returns a deferred -- having it fired when 'ready-to-use'.

In this way, we have a constructor that just returns the instance (and the user is responsible to make the bootstrapping call).