Remove dependance on external http library in client library

[ajvb]

Currently, the go client library utilizes Sling to do the HTTP communication. This is not required, and we should simply use the standard library.

[fuel-]

Hi there!

I am, somewhat, new to programming in go and am trying to improve my programming skills by helping out and contributing to other projects. I saw that this issue was marked as good for beginners and thought I would take a stab.

However I am getting stuck trying to build Kala using the instructions in the readme. I have attached a text file that shows my steps in cmd.
cmds-issued.txt

Is this an issue with my gopath or where I have my projects maybe?

Edit: Additionally I would be happy to document working through this to help with "Write out "Getting Started" guide #19"

[elimisteve]

I'm curious if Sling has been causing any problems or whether it completely just is about wanting fewer dependencies.

[ajvb]

@fuel- Hey! Thanks for leaving this comment. So it looks like you are missing https://github.com/tools/godep.

On a side note, Kala has had no testing in a Windows environment, so I'm not sure how well it will work. It shouldn't be UNIX specific, but somethings may break. Please feel free to email me directly if you are having any problems.

In regards to this issue, the reasoning is absolutely "wanting fewer dependencies" vs. it actually causing any real problems. No matter, it would be nice to just use the standard library directly.

[ajvb]

Closed by #126