Add support for http and socket transports

[dbarrosop]

Fixes #64

@narJH27 would you mind testing this branch?

If it works I will document the optional arg in the official documentation.

[coveralls]

Coverage decreased (-0.4%) to 79.288% when pulling db0b504 on dbarrosop/add_support_for_different_transports into 1f0b976 on develop.

[coveralls]

Coverage decreased (-0.4%) to 79.288% when pulling db0b504 on dbarrosop/add_support_for_different_transports into 1f0b976 on develop.

[narJH27]

Typo: self.transport instead of self.transrpot

[mirceaulinic]

I also noticed this one Implemantation :)

[narJH27]

Also, the socket transport can only be used by a script on the box rather than a script trying to connect to the box from the outside. In my testing, my script could connect to the box using a UNIX socket using pyeapi.connect(<host>) as opposed to pyeapi.client.connect(). Maybe you can look into that?

[dbarrosop]

Can you send your script and any relevant configuration? I just want to make sure I test your same exact conditions.

[narJH27]

@dbarrosop No relevant conditions as such. But my recollection of using pyeapi with unix sockets was as mentioned above. The script is nothing major, basically opening a connection to the box using the unix socket and calling one of napalm's methods, something like a get_bgp_neighbors_detail() which usually takes a few seconds to respond in the normal case.

[dbarrosop]

@narJH27 I don't really understand what you are asking for with this:

the socket transport can only be used by a script on the box rather than a script trying to connect to the box from the outside

Unix sockets are local by nature, you can't connect from the outside unless they are exposed via a TCP port, which is what the http and https transports are for.

[narJH27]

@dbarrosop Apologies for using the phrase from the outside. What I meant was a local script connecting to the UNIX socket on the box rather than an outside connection using HTTP/HTTPS.

[dbarrosop]

So this is done then. Merging.