#19 楼 @phun 哦，那看起来最后大家都是想到一块儿了，中间表结构的思路都是差不多的。

Controller, View Helper 没做，因为实际情况（例如 Ruby China 的场景）可能在 like_xxx 的过程有其他动作（创建通知，Event 之类的），所以就没有像其他 rails-engine 里面的 Gem 那样把整个链路给实现。

反正你最后也只会做一半放弃的

#7 楼 @u1452261116

http://react-homeland.herokuapp.com/

演示 OAuth 2 登录 Ruby China

#17 楼 @cao7113 以后不要等我，Just do it！

#12 楼 @cao7113 #14 楼 @phun

你们的做法也是这样吗？发出来探讨一下

AnyCable looks lovely and it'll be interesting to follow the new Rack specification. But Action Cable should work out-of-the-box with no additional servers or setups required beyond Puma. If there are options available that fulfill that criteria and are drop-in replacements, awesome, let's look at that. Also happy to accommodate whatever AnyCable might need, but haven't seen any requests.

So let's wait to see some real approaches that need the existing server extracted before we venture down that path.

Whatever benchmarks that were done against 5.0.0 should take another go against 5.0.1. Tons of Action Cable fixes for both performance and stability. But regardless of what that changes, the overall story will remain the same. Ruby is never going to win any Hello World shoot-out against C++ or microframeworks. That's as true for a regular 200 OK request as it is for a websockets connection. That doesn't mean we shouldn't seek to improve performance, and options like AnyCable might do so dramatically, just that we should have realistic expectations of where things go.

For Basecamp 3, which Action Cable was developed for and extracted from, our main issue has been less raw websocket performance and more just doing the work that is needed across that wire. Kinda like how doing 2,000 req/sec on a "Hello World" 200 OK is a bit irrelevant compared to building a real app. It's extremely unlikely that the overhead of your underlying server is going to be the bottleneck. It's more likely to be your application logic.

All depends on your use case, of course. And happy to see others push the performance of Action Cable further. As-is, it's plenty good enough to run a major app like Basecamp 3.

by @dhh

https://groups.google.com/d/msg/rubyonrails-core/PSbhfZ2LCWo/XQAnkP2CEQAJ

验证码就是故意那么做，防读取的啊

有一下几种可能

1. 别人或许收到了很多，没法一一回复，你想多了
2. 也许别人要求写在哪里，你没符合要求，却投简历过去，浪费了别人阅读时间，你说别人还会不会答复你？
3. 如果连电话都没有来，说明对方压根对你不感兴趣（当然也有可能看漏了邮件）

所以，还是不要想太多了，对方不要你也不一定说明你不行，而是你不是他们想要的而已。

#7 楼 @kikyous 可以的

#5 楼 @kikyous 补了

看情况，有时候不要关联删除比较好

#6 楼 @jasonZYJ 今天的日志里面只有这两条

#4 楼 @jasonZYJ

01.80.173.136 - - [07/Feb/2017:09:00:50 +0800] "GET /notifications HTTP/2.0" 200 4569 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 10_3 like Mac OS X) AppleWebKit/603.1.20 (KHTML, like Gecko) turbolinks-app, ruby-china, official, iOS, version:2.1.3" 0.564 0.564 .
101.80.173.136 - - [07/Feb/2017:09:00:54 +0800] "GET /api/v3/notifications/unread_count HTTP/2.0" 200 768 "-" "Ruby China/2.1.3 (org.ruby-china.app; build:53; iOS 10.3.0) Alamofire/4.2.0" 0.013 0.013 .

这个 IP 是你的 iOS 访问的，我要的是你说访问不了的 IP 地址

告诉我你无法访问的 IP，打开 ip.cn 查看

一直是这样么？

1. 搞测试就别 push 到 rubygems.org 了，浪费公共资源。
2. 真正的问题是，你不应该配置 spec.metadata['allowed_push_host']，http:// 可能被认为不安全，给拒绝了

赶紧申请用 @poshboytl 他们公司的 https://zhiren.com https://tower.im 服务

估计那里有 unset DYLD_LIBRARY_PATH

GitLab 就可以了，提交 Issue，我们用来交周报

不能

好像是不行，echo 可以，env 或者 irb 里面用 ENV["DYLD_LIBRARY_PATH"] 都没有

source ~/.bash_profile

这个做了没？

或者尝试：

export DYLD_LIBRARY_PATH=123
echo $DYLD_LIBRARY_PATH

#14 楼 @leiz_me 需要 mocha

#10 楼 @helapu 核心那段 C 也不是我写的，我只是找到个好方案，适当封装了一下，便于使用