Separate API and implementation about hammock

[pepegar]

Hey @ipsq ! I've been thinking about this for some time too, but haven't had time to do it so far.

Do you want to champion it? contributions are open :)

I think the refactor would be simple, just creating a new module hammock-apache-http (or something like that) and remove that part from the core.

[mhriemers]

Sure, will look at it this afternoon! What do you want to do with the versioning? Since this would be a breaking change for some.

[pepegar]

awesome! Yeah, I think we should release a new minor after this change (0.9.0), since we're still in 0 as major

[mhriemers]

Maybe the default JS implementation should also be moved to its own submodule. Let me know what you guys think. I can imagine some scenarios where people want to use the node request api directly without a polyfill or something like that.

[pepegar]

I think it's better to provide one by default in that case, because it doesn't add any other dependency and is the only one available in that platform. What do you think?

[mhriemers]

Yeah, that's fair I guess. Was just something that popped in my mind whilst I was refactoring.

[pepegar]

closed by #156

Thanks @ipsq !

BTW, https://oss.sonatype.org/content/repositories/snapshots/com/pepegar/hammock-core_2.12/0.8.7+52-af7aee56-SNAPSHOT/ has been published (notice that it's a snapshot). If you want you can test-drive it and if it works for you I will release a 0.9.0!