Agreed. Calling that 'pull style' is a little confusing to me, but ultimately the goal is totally right: we can model a web server as a function of an http request data structure (or object or whatever) that returns a response data structure. This makes handler / middleware composition the same as function composition, rather than requiring some kind of special chaining.
Makes sense to go Apache 2 if you plan on making sure that patent grant isn't an issue, but Apache 2 turns me off because of verbosity. If it's a big, important project, Apache 2 might be worth looking into, but for most of the stuff I'm working on I went with MIT because it's approachable by laypeople (non-lawyers) - aka developers.
6 comments
1 u/zhong_j_yu 17 Jul 2015 02:12
I think a better API is to design response body as a source, not as a sink. See my article Don't give me an http response; I'll give you one
1 u/Mapoosa 18 Jul 2015 08:47
Agreed. Calling that 'pull style' is a little confusing to me, but ultimately the goal is totally right: we can model a web server as a function of an http request data structure (or object or whatever) that returns a response data structure. This makes handler / middleware composition the same as function composition, rather than requiring some kind of special chaining.
0 u/zhong_j_yu 20 Jul 2015 03:47
yes. it's very easy to program intermediaries in bayou.io
0 u/dchem [OP] 19 Jul 2015 03:17
Why Apache 2 though?
0 u/zhong_j_yu 20 Jul 2015 03:46
You mean the license? I don't know, just following the licensing of other similar projects:) What do you think?
0 u/dchem [OP] 21 Jul 2015 03:09
Makes sense to go Apache 2 if you plan on making sure that patent grant isn't an issue, but Apache 2 turns me off because of verbosity. If it's a big, important project, Apache 2 might be worth looking into, but for most of the stuff I'm working on I went with MIT because it's approachable by laypeople (non-lawyers) - aka developers.