[erlang-questions] Split Cowboy's acceptor and HTTP code

[Loïc Hoguin]

Hello,

I have received a lot of feedback on Cowboy recently, especially at the 
Erlang Factory. The main concern people seem to have today is that many 
of you seem to want to use Cowboy's acceptor code and transport 
abstraction, but don't want to include the HTTP components.

I argued until now that you can always remove the HTTP modules from the 
release if you want, and that it's easier to work on improving both 
sides at the same time without the dependency, while still keeping in 
mind that the two parts would eventually get split before 1.0.

Considering the feedback, I'm wondering if now would be the time to 
split them.

Most people use rebar nowadays, so the dependency should be handled 
automatically. But I did receive a few comments before from people who 
liked the fact that Cowboy was a single package.

If the split happens, it will be right after the next version tag, 
0.6.0, and will most likely include a renaming of most modules all in a 
single commit. People who follow master will need to update their code 
immediately (I'll give a script to do that automatically), while others 
staying at 0.6.0 will have some time to make it happen.

If you don't want the split to happen at this point, you should probably 
reply to this mail so we can all discuss what should happen and when.

I hope it won't be too much trouble on everyone, the module renaming 
script should take care of most of it.

Thanks for your feedback, as always!

-- 
Loïc Hoguin
Erlang Cowboy
Nine Nines