
1 vitovan Oct 1, 2015 WTF! |
2 shuson Oct 1, 2015 不得不说老毛子果然是战斗民族 |
3 LazyZhu Oct 1, 2015 Niubility. |
4 vitovan Oct 1, 2015 |
5 riaqn Oct 1, 2015 用 js 来配置 nginx ? 是这样理解么…… |
6 xfspace Oct 1, 2015 via iPad 这功能。。。不错 |
7 emric Oct 1, 2015 简直前端狗的春天. |
8 db520 Oct 1, 2015 via Android lua 怎么办,有必要又造一个轮子吗? |
9 wdlth Oct 1, 2015 nodeGINX 要出现了? |
10 dndx Oct 1, 2015 OpenResty 表示压力很大。 |
11 MaiCong Oct 1, 2015 via iPad 表示期待 |
12 joyee Oct 1, 2015 We run a separate VM for each request, so there ’ s no need for garbage collection. 谁敢做下小白鼠? |
16 xiqingongzi Oct 1, 2015 我说 nginx 的 wiki 咋改版了呢 |
17 Robling Oct 1, 2015 不是作为一个模块而是直接嵌入到里面么? |
18 cylin Oct 1, 2015 好棒(//) |
19 paulw54jrn Oct 1, 2015 评论褒贬不一啊 ``` You're using JS, which helps the expressivity issue a bit, but in exchange it's inheriting all the problems of JS, and squishing them into my web server, and with no apparent framework for making common and dangerous tasks simple and safe. For example, the comment in your second says that unary + applied to a string will "convert upstream number to integer", but that's not true. It converts a String to a Number (including the "number" NaN). +"0.5" is the Number 0.5, which will send you to the server "my_upstream0.5". +"X" is NaN, which will send you to "my_upstreamNaN". Unary + supports scientific notation, too, so "1.2e-100" becomes "my_upstream1.2e-100". It supports hexadecimal integers, too, though that's les interesting when you clamp to [0,1]. These mis-routings are probably harmless in this case, but it's not hard to imagine similar situations where they're not. If the authors of a feature can't use it safely in their trivial demo examples in the product announcement, what confidence do I have that I'm going to be able to make it work reliably and securely on an actual production website? --JS Dude ``` |
20 secondwtq Oct 1, 2015 貌似开发者的意思是希望这东西仅仅用来配置 nginx 服务程序,而不是做出一个完整的服务。和 OpenResty 之类还是有分别的。 |
21 zsj950618 Oct 2, 2015 via Android 世界是 Javascript 的 |